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]

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

On Tue, Apr 27, 2010 at 05:38:50PM +0200, Arnd Bergmann wrote:
> On Tuesday 27 April 2010, Jörn Engel wrote:
> > On Tue, 27 April 2010 17:27:19 +0200, John Kacur wrote:
> > > 
> > > Hasn't the "current" merge window been over with for weeks? I was assuming 
> > > that bkl push down, or other bkl patches are for the next merge window.
> > 
> > That's what I was thinking.  But some of the bkl related discussion gave
> > me the impression that such patches were still being merged.  So I
> > wanted to be sure.
> 
> Yes, just queue it for the 2.6.35-rc1 window and make sure it shows up in
> linux-next, or send a replacement patch with your Ack or S-o-b so we can
> put it into the BKL queue.
> 
> 	Arnd


I've applied this series in bkl/ioctl, it passed allyesconfig in sparc.
I will apply the others from you and John tomorrow or so (and will enjoy
my part as well). Jörn, please queue this patch if you want to, as you prefer,
we can host it as well if necessary.

Linus I hope you don't mind but I've dropped the .bkl_ioctl renaming.
In fact it had conflicts with several trees in Linux-next and now that
we are about to pushdown in every ioctl users, this would be an
unnecessary step I think.

Thanks.

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