linux-kernel - Re: [GIT PATCH] TTY patches for 2.6.36

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:	Fri, 6 Aug 2010 12:38:36 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Greg KH <gregkh@...e.de>, Arnd Bergmann <arnd@...db.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] TTY patches for 2.6.36

On Fri, Aug 6, 2010 at 12:45 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>
> Wouldn't it make more sense to simply turn it on as Linus suggested ?

I really do want the whole "there can be only one" highlander part.

Go all Christopher Lambert on it, and cut it off at the head so that
it cannot resurface even by mistake. IOW, remove the config option
entirely, and remove the #ifdef's that switch between the BKL and
mutex case.

Otherwise somebody will enable the BKL code, and we'll miss the
testing for that case. And getting testing is what the whole merge
window is all about.

I also don't want the BKL to show up in grep, even if the config
option for it were to be impossible to enable. If we've gotten far
enough that we can get rid of the BKL in the tty layer, we really
should get rid of it. Not leave it in some zombie limbo state.

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