linux-kernel - Re: [PATCH v2] init: Scream bloody murder if interrupts are enabled too early

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, 8 Mar 2013 13:55:40 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ard van Breemen <ard@...egraafnet.nl>
Subject: Re: [PATCH v2] init: Scream bloody murder if interrupts are enabled
 too early

On Fri, 08 Mar 2013 09:48:12 -0500 Steven Rostedt <rostedt@...dmis.org> wrote:

> Also, while examining other warnings in init/main.c, I found two other
> locations that deserve a bloody murder scream if their conditions are
> hit, and updated them accordingly.

So the whole effect of this patch is to spew a larger volume of
unuseful stuff (such as uninteresting stack traces) onto the console so
people are more likely to notice it?  Hmpf.  I think I prefer

akpm3:/usr/src/25> banner "OMG\!\!"      
####### #     #  #####    ###     ###
#     # ##   ## #     #   ###     ###
#     # # # # # #         ###     ###
#     # #  #  # #  ####    #       #
#     # #     # #     #
#     # #     # #     #   ###     ###
####### #     #  #####    ###     ###


Maybe we should reduce the amount of goop we printk out at boot
instead ;)

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