linux-kernel - Re: [patch] Printk kernel version in WARN

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: <20071118004218.GA26865@elte.hu>
Date:	Sun, 18 Nov 2007 01:42:18 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, tglx@...x.de
Subject: Re: [patch] Printk kernel version in WARN_ON


* Arjan van de Ven <arjan@...radead.org> wrote:

> ok so how about putting the same into dump_stack() instead? (see 
> below) added bonus is that it's now present for all dumps that use 
> dump_stack(), not just WARN_ON() (the format I copied from the exact 
> line used by oopses)

nice! I did things like this in -rt because it really helps to know 
which process does a WARN_ON() or raw dump_stack().

> Signed-off-by: Arjan van de Ven <arjan@...ux.intel.com>

Acked-by: Ingo Molnar <mingo@...e.hu>

unless objections we'll put this into the x86 git tree.

	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/