linux-kernel - Re: [PATCH] x86 NMI: Be smarter about invoking panic() inside NMI handler.

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: <CANz0V+5ayWh3-xR1i4nCqTGF+6x+f7mOeokEhCCXhvG3a3pFhw@mail.gmail.com>
Date:	Tue, 20 Mar 2012 13:57:41 -0400
From:	"Andrei E. Warkentin" <andrey.warkentin@...il.com>
To:	linux-kernel@...r.kernel.org
Cc:	kgdb-bugreport@...ts.sourceforge.net, jason.wessel@...driver.com,
	Andrei Warkentin <andrey.warkentin@...il.com>
Subject: Re: [PATCH] x86 NMI: Be smarter about invoking panic() inside NMI handler.

Hi,

2012/3/1 Andrei Warkentin <andrey.warkentin@...il.com>:
> If two (or more) unknown NMIs arrive on different CPUs, there
> is a large chance both CPUs will wind up inside panic(). This
> is fine, unless you want to enter KDB - KDB cannot round up
> all CPUs, because some of them are stuck inside
> panic_smp_self_stop with NMI latched. This is
> easy to replicate with QEMU. Boot with -smp 4 and
> send NMI using the monitor.
>
> Solution for this - attempt to enter panic() from NMI
> handler. If panic() is already active in the system,
> just exit out of the NMI handler. This lets KDB round
> up CPUs.
>
> Signed-off-by: Andrei Warkentin <andrey.warkentin@...il.com>
> ---

Any feedback on this? Who are the right maintainers to bug about this?

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