linux-kernel - Re: [GIT, RFC] Killing the Big Kernel Lock II

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: <201003311730.31379.arnd@arndb.de>
Date:	Wed, 31 Mar 2010 16:30:31 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Jiri Kosina <jkosina@...e.cz>,
	Frederic Weisbecker <fweisbec@...il.com>,
	linux-kernel@...r.kernel.org, Matthew Wilcox <matthew@....cx>,
	Thomas Gleixner <tglx@...utronix.de>, jblunck@...e.de,
	Alan Cox <alan@...ux.intel.com>, Ingo Molnar <mingo@...e.hu>,
	gregkh@...e.de, linux-usb@...r.kernel.org
Subject: Re: [GIT, RFC] Killing the Big Kernel Lock II

On Monday 29 March 2010, Andi Kleen wrote:
> > > > The patch looks correct, but I probably wouldn't bother with the rename,
> > > > and simply drop the BKL in the caller.
> > > 
> > > I think a rename is better, I take compile errors over subtle
> > > breakage any day.
> > 
> > ok, fine with me.
> 
> I updated the git tree removing the unneeded serial change. Feel free to pull.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc-2.6.git usb-bkl

Looks good to me. I guess it makes sense to merge this through Greg's USB
tree. AFAICT the only prerequisite to this series is to have CONFIG_BKL
enabled in Kconfig. Shall we add a that to 2.6.34 as 'def_bool y' for
preparation so we can queue up patches like this in maintainer trees?

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