linux-kernel - Re: Question about percpu_free

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160307135356.GS3577@linux.vnet.ibm.com>
Date:	Mon, 7 Mar 2016 05:53:56 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Daeho Jeong <daeho.jeong@...sung.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Question about percpu_free_rwsem function

On Mon, Mar 07, 2016 at 03:28:11AM +0000, Daeho Jeong wrote:
> Hi,
> 
> I got a trouble while I am developing a patch for EXT4 filesytem.
> Actually, I used a percpu rw semaphore in my patch and there was no
> problem when I built EXT4 filesystem as built-in mode. However, when
> kbuild auto build robot built EXT4 filesystem with my patch as a "module",
> a bulid error occurred because percpu_free_rwsem() function is not exported.
> 
> I noticed that other functions except percpu_free_rwsem() were exported in 2015.
> Is there any reason for percpu_free_rwsem() not to be exported?
> If I need the function to be exported, should I do that in my patch? :-)

Sounds like a question for the ext4 maintainers.  You can find them in
the MAINTAINERS file.

							Thanx, Paul