linux-kernel - Re: [GIT PULL v2] Preparation for BKL'ed ioctl removal

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: <20100428133702.GA3193@elte.hu>
Date:	Wed, 28 Apr 2010 15:37:02 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Al Viro <viro@...iv.linux.org.uk>,
	Jan Blunck <jblunck@...e.de>, John Kacur <jkacur@...hat.com>
Subject: Re: [GIT PULL v2] Preparation for BKL'ed ioctl removal

* Frederic Weisbecker <fweisbec@...il.com> wrote:

> [...]
> 
> That said, once we reach that point with 4 users of bkl remaining, may be 
> that will be time to buy such hardware for a symbolic $1 in obscure places 
> and do the tests. Or just git-rm if we are too lazy.

Precisely. Note that the actual value of BKL-covered code shrinks every time 
we push the BKL out of commonly used code.

So even if there's still usage sites around, there will be a point where it 
makes sense to just desupport it or do a final, crude conversion. If there are 
no active users who are willing to help us debug potential bugs then there's 
frankly no value in us being just as careful with those drivers as we are with 
other, more commonly used code.

For the rest, lockdep & softlockup detector will be plenty enough to debug any 
bugs that may slip through - just like you did it with ReiserFS.

	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/