linux-kernel - Re: printk() vs tty

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: <1324041955.18942.97.camel@twins>
Date:	Fri, 16 Dec 2011 14:25:55 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Ted Ts'o <tytso@....edu>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Greg KH <greg@...ah.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: printk() vs tty_io

On Thu, 2011-12-15 at 09:08 -0800, Linus Torvalds wrote:
>    Peter, why do you want to try to work from under the rq lock?

As Ingo already mentioned, there was no strong reason. The rationale was
reducing surprise lockups like that xtime_lock thing. Also, there are
various WARNs in the scheduler code that could possibly trigger and
cause a deadlock.

Then again, they're not supposed to trigger and mostly if they do we
don't get an insta deadlock (at least not on the consoles I've used),
but there is the possibility of course.

I'm not sure the WARNs are enough reason to invent a new async printk
facility, but if you feel strongly about that I can look into doing it.
--
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/