linux-kernel - Re: [PATCH 04/12] BKL: Remove BKL from autofs4

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4C926DFC.1090600@zytor.com>
Date:	Thu, 16 Sep 2010 12:20:28 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	linux-kernel@...r.kernel.org, Ian Kent <raven@...maw.net>,
	autofs@...ux.kernel.org
Subject: Re: [PATCH 04/12] BKL: Remove BKL from autofs4

On 09/16/2010 10:55 AM, Arnd Bergmann wrote:
> On Thursday 16 September 2010 19:49:53 H. Peter Anvin wrote:
>> On 09/16/2010 10:46 AM, Arnd Bergmann wrote:
>>> autofs4 uses the BKL only to guard its ioctl operations.
>>> This can be trivially converted to use a mutex, as we have
>>> done with most device drivers before.
>>>
>>> Signed-off-by: Arnd Bergmann <arnd@...db.de>
>>> Cc: "H. Peter Anvin" <hpa@...or.com>
>>> ---
>>>  fs/autofs4/root.c |   12 +++++++-----
>>>  1 files changed, 7 insertions(+), 5 deletions(-)
>>
>> You may want to Cc: the maintainer, Ian Kent.
> 
> Ah, sorry about this. I looked at the wrong MAINTAINERS entry.
> 
> I also forgot to Cc you about autofs3, adding more to the confusion. ;)
> 
> Do you think the time has come to move autofs3 to drivers/staging
> as we deprecate the BKL?
> 

I'm leaving that up to Ian.  I have offered for years to just plain kill
off autofs3.

	-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/