linux-kernel - Re: CPU softlockup due to smp_call

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] [day] [month] [year] [list]

Date:	Thu, 05 Apr 2012 15:51:00 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Sasha Levin <levinsasha928@...il.com>
CC:	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Dave Jones <davej@...hat.com>, kvm@...r.kernel.org,
	"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>
Subject: Re: CPU softlockup due to smp_call_function()

On 04/05/2012 03:32 PM, Sasha Levin wrote:
> >
> > It would be good to enhance smp_call_function_*() to do this
> > automatically when it happens - it's spinning there anyway, so it might
> > as well count the iterations and NMI the lagging cpu if it waits for too
> > long.
>
> What do you think about modifying the softlockup detector to NMI all
> CPUs if it's going to panic because it detected a lockup?

Fine by me.  The triggering cpu should be dumped first though.

We lose knowledge of exactly which cpu is hung, but it should usually be
easily seen from the traces (the exceptional case would be a busy server
that is handling a lot of IPIs at the moment we trigger the traces).

-- 
error compiling committee.c: too many arguments to function

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