linux-kernel - Re: cosmetic printk() issue with lockdep warning in arch/x86/kernel/alternative.c

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] [day] [month] [year] [list]

Message-ID: <20120629125845.GA32730@gmail.com>
Date:	Fri, 29 Jun 2012 14:58:45 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Kay Sievers <kay@...y.org>, Steven Rostedt <rostedt@...dmis.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, Greg Kroah-Hartmann <greg@...ah.com>,
	Lennart Poettering <lennart@...ttering.net>
Subject: Re: cosmetic printk() issue with lockdep warning in
 arch/x86/kernel/alternative.c


* Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:

> On Wed, 2012-06-27 at 12:49 +0200, Kay Sievers wrote:
> > All we want is a reliable printk
> 
> We too, but we define reliable differently. I want printk() to 
> dump data ASAP so that it has better chance to get out of the 
> system and onto my console in case of a crash. I don't give a 
> rats arse about interleaved text, any text is better than no 
> text.

I actually *fixed* bugs in the past when I saw interleaved text 
printed from multiple CPUs, it told me how narrow and SMP 
dependent a particular race/crash was.

So even interleaving, although annoying most of the time, can be 
useful in some other places.

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/