linux-kernel - Re: [PATCH v3 00/10] BKL conversion in tty layer

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: <20100517153055.GA28137@suse.de>
Date:	Mon, 17 May 2010 08:30:55 -0700
From:	Greg KH <gregkh@...e.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
	Frederic Weisbecker <fweisbec@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	John Kacur <jkacur@...hat.com>,
	Al Viro <viro@...iv.linux.org.uk>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH v3 00/10] BKL conversion in tty layer

On Mon, May 17, 2010 at 02:41:30PM +0100, Alan Cox wrote:
> On Sat, 15 May 2010 22:59:46 +0200
> Arnd Bergmann <arnd@...db.de> wrote:
> 
> > This is the third attempt to get the BKL out of the
> > TTY code. This version goes much further than the
> > previous one, and eliminates most of the code I
> > had introduced there.
> 
> At this point I think the only way to make further progress is to
> actually push this stuff into the kernel on top of the BKL removal
> patches for the drivers and see what happens. Something will no doubt
> break but we can try and nail them in time or if not revert the series
> and try again next kernel.
> 
> The big nasty remaining after this is drivers/serial, which probably
> wants some serious reconstructive surgery to use kfifo etc. Either way
> its an independent problem to the stuff this lot tackles.
> 
> So this series
> 
> Acked-by: Alan Cox <alan@...ux.intel.com>

I'd prefer to do this for .36, not for .35.  Arnd, I'll be glad to queue
these patches up to the tty development tree after .35-rc1 is out, so it
gets lots of testing in the linux-next tree, is that ok?  If so, can you
resend them to me at that time?

thanks,

greg k-h
--
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/