linux-kernel - Re: Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr problem

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: <11274.1281061410@redhat.com>
Date:	Fri, 06 Aug 2010 03:23:30 +0100
From:	David Howells <dhowells@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	dhowells@...hat.com, Herbert Xu <herbert@...dor.hengli.com.au>,
	gregkh@...e.de, linux-kernel@...r.kernel.org,
	linux-crypto@...r.kernel.org
Subject: Re: Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr problem

Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> People always think that their magical code is so important. I tell
> you up-front that is absolutely is not. Just remove the crap entirely,
> please.

Even if he does remove it, that still leaves the problem that modprobe can be
invoked and fail before tty_init() gets called:-/

I wonder if tty_init() should be moved up, perhaps to immediately after
chrdev_init().

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