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]
Date:	Mon, 19 May 2008 15:17:22 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jonathan Corbet <corbet@....net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Alexander Viro <viro@....linux.org.uk>,
	linux-kernel@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH, RFC] Char dev BKL pushdown v2


* Jonathan Corbet <corbet@....net> wrote:

> OK, since the previous announcement, I've revisited all of the open() 
> functions which didn't get lock_kernel() calls the first time around. 
> Alan pointed out that even a completely empty open() might, in fact, 
> need to acquire the BKL, so now they all do.  Hopefully, this 
> completes this work (at this level - there's plenty of down-pushing to 
> do within subsystems).

cool stuff! :-)

> There's a new tree with this stuff:
> 
> 	git://git.lwn.net/linux-2.6.git bkl-removal
> 
> Stephen, might it be about time to pull this into linux-next and see 
> what explodes?
> 
> If others have BKL-removal patches which look like 2.6.27 material, 
> I'll happily collect them in this tree.

i'm wondering how this should best interact with the kill-the-BKL bits 
that attack it all from the infrastructure side. Your bits are the safer 
ones, so i guess i'll try to track your changes from my branch to 
increase testing of it all?

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ