linux-kernel - Re: [PATCH] printk: Revert the buffered-printk() changes for now

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: <20120625140748.GB1301@gmail.com>
Date:	Mon, 25 Jun 2012 16:07:48 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Kay Sievers <kay@...y.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Fengguang Wu <fengguang.wu@...el.com>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] printk: Revert the buffered-printk() changes for now


* Kay Sievers <kay@...y.org> wrote:

> > Kernel policy is that kernel bugs introduced during the 
> > merge window are fixed by those who introduced them, or the 
> > changes get reverted. The kernel project uses a very 
> > user-friendly process to resolve regressions and in the 
> > worst case you as a developer have to suffer your changes 
> > reverted. Obviously timely fixes are preferred over invasive 
> > reverts.
> 
> That's true. this change is a trade, and the kernel self-tests 
> print-continuation-line-and-let-the-kernel-crash is currently 
> affected by the hugely improved integrity and reliability of 
> all the "normal" users.

Sigh, which part of the "no regressions" policy did you not 
understand?

Even if we ignored regressions (which we don't), you'd *STILL* 
be wrong: using printk to debug crashes (and to develop code in 
general) is one of its earliest and I'd say most important role.

And when do we need printk() output? Most of the time only when 
there's a problem with the system - such as a crash.

System logging is an arguably secondary role, and it should not 
degrade printk()s primary role.

Your flippant attitude towards printk quality is really sad.

Thanks,

	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/