linux-kernel - Re: [PATCH] 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]

Message-ID: <1362742682.31874.91.camel@gandalf.local.home>
Date:	Fri, 08 Mar 2013 06:38:02 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ard van Breemen <ard@...egraafnet.nl>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] init: Scream bloody murder if interrupts are enabled
 too early

On Fri, 2013-03-08 at 10:03 +0100, Ard van Breemen wrote:

> The original code was a few versions before the WARN macros.
> I think it's better to just change the printk to something like:
> WARN(1,"interrupts were enabled *very* early, fixing it\n")
> 

Yeah, I thought about updating to that, but I was lazy. I was hoping
nobody would notice. ;-)

OK, I'll send out -v2 as soon as I finish testing it.

Thanks,

-- Steve


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