linux-kernel - Re: [PATCH 1/7] logfs: push down BKL into ioctl function

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]

Date:	Tue, 27 Apr 2010 18:29:02 +0200 (CEST)
From:	John Kacur <jkacur@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	John Kacur <jkacur@...hat.com>,
	Jörn Engel <joern@...fs.org>,
	Arnd Bergmann <arnd@...db.de>,
	lkml <linux-kernel@...r.kernel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jan Blunck <jblunck@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 1/7] logfs: push down BKL into ioctl function



On Tue, 27 Apr 2010, Linus Torvalds wrote:

> 
> 
> On Tue, 27 Apr 2010, John Kacur wrote:
> >
> > You can ask Linus whether he'll take a convert unlocked_ioctl now or not.
> 
> Absolutely not.
> 
> I could imagine merging something like just the bkl_ioctl rename: if it 
> breaks, it won't compile, so there is little risk, and _if_ it helps the 
> next merge window I could merge it early.
> 
> But it looks like people are trying to avoid it entirely, and there is not 
> a way in *hell* I will take some big and scary "push BKL down" patch that 
> is clearly _not_ 99% mechanical and clearly _can_ introduce major and 
> subtle bugs while compiling. 
> 

Heh, that's exactly what I thought you would say, but still good to 
clarify it for everyone.

John 
--
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/