linux-kernel - Re: [PATCH 5/5] Always print panic message on current console

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: <20091012184224.GB20412@basil.fritz.box>
Date:	Mon, 12 Oct 2009 20:42:24 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Bernhard Walle <bernhard@...lle.de>,
	Andi Kleen <andi@...stfloor.org>, akpm@...uxfoundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] Always print panic message on current console

> It's called in the panic notifier atm.  Yeah sounds like kexec vs
> notifiers should be reordered a bit (or the current panic notifier
> should be split into notify and "yes we actually failed to do anything"
> cases).

I think it needs oops_begin() move over to a generalized panic_begin()
which is used everywhere there are multiple line panics.

oops_begin could do all these things, possibly with a new notifier.

This could also solve a couple of other open issues, like
currently we can have parallel panics deadlocking so doing proper
locking.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/