linux-kernel - [PATCH 0/2] x86, reboot: cleanup NMI and REBOOT

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

Message-Id: <1328907735-6226-1-git-send-email-dzickus@redhat.com>
Date:	Fri, 10 Feb 2012 16:02:13 -0500
From:	Don Zickus <dzickus@...hat.com>
To:	<x86@...nel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>, tony.luck@...el.com,
	seiji.aguchi@....com, ak@...ux.intel.com, mjg@...hat.com,
	levinsasha928@...il.com, Don Zickus <dzickus@...hat.com>
Subject: [PATCH 0/2] x86, reboot: cleanup NMI and REBOOT_IRQ

After dealing with pstore conversations about spin locks, I had an idea
to simplify the native_smp_stop_other_cpus() path by using both REBOOT_IRQ
and NMI instead of using either or.

I also cleaned up a WARN_ON splat from rescheduling.

Tested 10 panics on my core2 quad using 'echo c > /proc/sysrq-trigger' and
panic=10 on the commandline.  The machine panic'd and rebooted succesfully
all 10 times.  Though only the first time did I see the WARN_ON splat, the
other 9 times I couldn't duplicate it.

Don Zickus (2):
  x86, reboot: revert stop_other_cpus to using IRQ with NMI fallback
  x86, reschedule: check to see if system is shutting down

 arch/x86/kernel/smp.c |  104 +++++++++++++++++++++++--------------------------
 1 files changed, 49 insertions(+), 55 deletions(-)

-- 
1.7.7.6

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