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

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: <20100324222324.GA31154@elte.hu>
Date:	Wed, 24 Mar 2010 23:23:24 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	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>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jonathan Corbet <corbet@....net>
Subject: Re: [GIT, RFC] Killing the Big Kernel Lock


* Arnd Bergmann <arnd@...db.de> wrote:

> I've built-tested an allmodconfig kernel with CONFIG_BKL disabled on x86_64, 
> i386, powerpc64, powerpc32, s390 and arm to make sure I catch all the 
> modules that depend on BKL, and I've been running various versions of this 
> tree on my desktop machine over the last few weeks while adding stuff.

Very nice work!

How about going one step further:

 - remove CONFIG_BKL altogether
 - remove all the remains of the BKL code in lib/kernel_lock.c and kernel/sched.c
 - turn lock_kernel() into a WARN_ONCE() and unlock_kernel() into a NOP.
 - ...
 - Celebrate! :-)

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