linux-kernel - Re: [announce] "kill the Big Kernel Lock (BKL)" tree

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: <482B56B9.8040703@zytor.com>
Date:	Wed, 14 May 2008 14:16:41 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Alexander Viro <viro@....linux.org.uk>
Subject: Re: [announce] "kill the Big Kernel Lock (BKL)" tree

Andi Kleen wrote:
> Alan Cox wrote:
>>> Most of the legacy users are unlikely to be latency problems,
>>> simply because only very few people (or nobody) still has that hardware
>>> and the code will never run.
>>>
>>> Also I wouldn't lose sleep over e.g. let ISDN continue using BKL forever.
>> Most 
> 
> Most?
> 
>> of the legacy users inflict that locking on other code - eg the ISN
>> use of the BKL directly impacts on the tty layer work.
> 
> So you just stick unlock_kernel()/lock_kernel() around the call
> to TTY (or similar to the entry points)
> 

... assuming that the ISDN code doesn't assume lock continuity across 
the TTY call.

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