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-next>] [day] [month] [year] [list]
Message-id: <37141218.258171457321291665.JavaMail.weblogic@ep2mlwas02b>
Date:	Mon, 07 Mar 2016 03:28:12 +0000 (GMT)
From:	Daeho Jeong <daeho.jeong@...sung.com>
To:	"paulmck@...ux.vnet.ibm.com" <paulmck@...ux.vnet.ibm.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:	Daeho Jeong <daeho.jeong@...sung.com>
Subject: Question about percpu_free_rwsem function

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? :-)

Best Regards,

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ