From: "河合英宏 / KAWAI,HIDEHIRO" <hidehiro.kawai.ez@hitachi.com> To: "'Borislav Petkov'" <bp@alien8.de> Cc: "Jonathan Corbet" <corbet@lwn.net>, "Peter Zijlstra" <peterz@infradead.org>, "Ingo Molnar" <mingo@kernel.org>, "Eric W. Biederman" <ebiederm@xmission.com>, "H. Peter Anvin" <hpa@zytor.com>, "Andrew Morton" <akpm@linux-foundation.org>, "Thomas Gleixner" <tglx@linutronix.de>, "Vivek Goyal" <vgoyal@redhat.com>, "Baoquan He" <bhe@redhat.com>, "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>, "x86@kernel.org" <x86@kernel.org>, "kexec@lists.infradead.org" <kexec@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "Steven Rostedt" <rostedt@goodmis.org>, "Michal Hocko" <mhocko@kernel.org>, "Ingo Molnar" <mingo@redhat.com>, "平松雅巳 / HIRAMATU,MASAMI" <masami.hiramatsu.pt@hitachi.com> Subject: RE: Re: [V6 PATCH 1/6] panic/x86: Fix re-entrance problem due to panic on NMI Date: Fri, 11 Dec 2015 00:23:51 +0000 [thread overview] Message-ID: <04EAB7311EE43145B2D3536183D1A84454A50151@GSjpTKYDCembx31.service.hitachi.net> (raw) In-Reply-To: <20151210154136.GA4762@pd.tnic> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="utf-8", Size: 7642 bytes --] > From: Borislav Petkov [mailto:bp@alien8.de] [...] > Looks better. > > Did some comments cleanup and nmi_panic() macro reformatting so that it > is more readable and ended up applying this: Thanks a lot! Hidehiro Kawai Hitachi, Ltd. Research & Development Group > --- > From: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> > Date: Thu, 10 Dec 2015 10:46:26 +0900 > Subject: [PATCH] panic, x86: Fix re-entrance problem due to panic on NMI > > If panic on NMI happens just after panic() on the same CPU, panic() is > recursively called. Kernel stalls, as a result, after failing to acquire > panic_lock. > > To avoid this problem, don't call panic() in NMI context if we've > already entered panic(). > > For that, introduce nmi_panic() macro to reduce code duplication. In > the case of panic on NMI, don't return from NMI handlers if another CPU > already panicked. > > Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> > Acked-by: Michal Hocko <mhocko@suse.com> > Cc: Aaron Tomlin <atomlin@redhat.com> > Cc: Andrew Morton <akpm@linux-foundation.org> > Cc: Andy Lutomirski <luto@kernel.org> > Cc: Baoquan He <bhe@redhat.com> > Cc: Chris Metcalf <cmetcalf@ezchip.com> > Cc: David Hildenbrand <dahi@linux.vnet.ibm.com> > Cc: Don Zickus <dzickus@redhat.com> > Cc: "Eric W. Biederman" <ebiederm@xmission.com> > Cc: Frederic Weisbecker <fweisbec@gmail.com> > Cc: Gobinda Charan Maji <gobinda.cemk07@gmail.com> > Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com> > Cc: "H. Peter Anvin" <hpa@zytor.com> > Cc: Ingo Molnar <mingo@kernel.org> > Cc: Javi Merino <javi.merino@arm.com> > Cc: Jonathan Corbet <corbet@lwn.net> > Cc: kexec@lists.infradead.org > Cc: linux-doc@vger.kernel.org > Cc: lkml <linux-kernel@vger.kernel.org> > Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> > Cc: Michal Nazarewicz <mina86@mina86.com> > Cc: Nicolas Iooss <nicolas.iooss_linux@m4x.org> > Cc: Peter Zijlstra <peterz@infradead.org> > Cc: Prarit Bhargava <prarit@redhat.com> > Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk> > Cc: Rusty Russell <rusty@rustcorp.com.au> > Cc: Seth Jennings <sjenning@redhat.com> > Cc: Steven Rostedt <rostedt@goodmis.org> > Cc: Thomas Gleixner <tglx@linutronix.de> > Cc: Ulrich Obergfell <uobergfe@redhat.com> > Cc: Vitaly Kuznetsov <vkuznets@redhat.com> > Cc: Vivek Goyal <vgoyal@redhat.com> > Link: http://lkml.kernel.org/r/20151210014626.25437.13302.stgit@softrs > [ Cleanup comments, fixup formatting. ] > Signed-off-by: Borislav Petkov <bp@suse.de> > --- > arch/x86/kernel/nmi.c | 16 ++++++++++++---- > include/linux/kernel.h | 20 ++++++++++++++++++++ > kernel/panic.c | 16 +++++++++++++--- > kernel/watchdog.c | 2 +- > 4 files changed, 46 insertions(+), 8 deletions(-) > > diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c > index 697f90db0e37..292a24bd0553 100644 > --- a/arch/x86/kernel/nmi.c > +++ b/arch/x86/kernel/nmi.c > @@ -231,7 +231,7 @@ pci_serr_error(unsigned char reason, struct pt_regs *regs) > #endif > > if (panic_on_unrecovered_nmi) > - panic("NMI: Not continuing"); > + nmi_panic("NMI: Not continuing"); > > pr_emerg("Dazed and confused, but trying to continue\n"); > > @@ -255,8 +255,16 @@ io_check_error(unsigned char reason, struct pt_regs *regs) > reason, smp_processor_id()); > show_regs(regs); > > - if (panic_on_io_nmi) > - panic("NMI IOCK error: Not continuing"); > + if (panic_on_io_nmi) { > + nmi_panic("NMI IOCK error: Not continuing"); > + > + /* > + * If end up here, it means we have received an NMI while > + * processing panic(). Simply return without delaying and > + * re-enabling NMI. > + */ > + return; > + } > > /* Re-enable the IOCK line, wait for a few seconds */ > reason = (reason & NMI_REASON_CLEAR_MASK) | NMI_REASON_CLEAR_IOCHK; > @@ -297,7 +305,7 @@ unknown_nmi_error(unsigned char reason, struct pt_regs *regs) > > pr_emerg("Do you have a strange power saving mode enabled?\n"); > if (unknown_nmi_panic || panic_on_unrecovered_nmi) > - panic("NMI: Not continuing"); > + nmi_panic("NMI: Not continuing"); > > pr_emerg("Dazed and confused, but trying to continue\n"); > } > diff --git a/include/linux/kernel.h b/include/linux/kernel.h > index 350dfb08aee3..750cc5c7c999 100644 > --- a/include/linux/kernel.h > +++ b/include/linux/kernel.h > @@ -446,6 +446,26 @@ extern int sysctl_panic_on_stackoverflow; > extern bool crash_kexec_post_notifiers; > > /* > + * panic_cpu is used for synchronizing panic() and crash_kexec() execution. It > + * holds a CPU number which is executing panic() currently. A value of > + * PANIC_CPU_INVALID means no CPU has entered panic() or crash_kexec(). > + */ > +extern atomic_t panic_cpu; > +#define PANIC_CPU_INVALID -1 > + > +/* > + * A variant of panic() called from NMI context. We return if we've already > + * panicked on this CPU. > + */ > +#define nmi_panic(fmt, ...) \ > +do { \ > + int cpu = raw_smp_processor_id(); \ > + \ > + if (atomic_cmpxchg(&panic_cpu, PANIC_CPU_INVALID, cpu) != cpu) \ > + panic(fmt, ##__VA_ARGS__); \ > +} while (0) > + > +/* > * Only to be used by arch init code. If the user over-wrote the default > * CONFIG_PANIC_TIMEOUT, honor it. > */ > diff --git a/kernel/panic.c b/kernel/panic.c > index 4b150bc0c6c1..3344524cf6ff 100644 > --- a/kernel/panic.c > +++ b/kernel/panic.c > @@ -61,6 +61,8 @@ void __weak panic_smp_self_stop(void) > cpu_relax(); > } > > +atomic_t panic_cpu = ATOMIC_INIT(PANIC_CPU_INVALID); > + > /** > * panic - halt the system > * @fmt: The text string to print > @@ -71,17 +73,17 @@ void __weak panic_smp_self_stop(void) > */ > void panic(const char *fmt, ...) > { > - static DEFINE_SPINLOCK(panic_lock); > static char buf[1024]; > va_list args; > long i, i_next = 0; > int state = 0; > + int old_cpu, this_cpu; > > /* > * Disable local interrupts. This will prevent panic_smp_self_stop > * from deadlocking the first cpu that invokes the panic, since > * there is nothing to prevent an interrupt handler (that runs > - * after the panic_lock is acquired) from invoking panic again. > + * after setting panic_cpu) from invoking panic() again. > */ > local_irq_disable(); > > @@ -94,8 +96,16 @@ void panic(const char *fmt, ...) > * multiple parallel invocations of panic, all other CPUs either > * stop themself or will wait until they are stopped by the 1st CPU > * with smp_send_stop(). > + * > + * `old_cpu == PANIC_CPU_INVALID' means this is the 1st CPU which > + * comes here, so go ahead. > + * `old_cpu == this_cpu' means we came from nmi_panic() which sets > + * panic_cpu to this CPU. In this case, this is also the 1st CPU. > */ > - if (!spin_trylock(&panic_lock)) > + this_cpu = raw_smp_processor_id(); > + old_cpu = atomic_cmpxchg(&panic_cpu, PANIC_CPU_INVALID, this_cpu); > + > + if (old_cpu != PANIC_CPU_INVALID && old_cpu != this_cpu) > panic_smp_self_stop(); > > console_verbose(); > diff --git a/kernel/watchdog.c b/kernel/watchdog.c > index 18f34cf75f74..b9be18fae154 100644 > --- a/kernel/watchdog.c > +++ b/kernel/watchdog.c > @@ -351,7 +351,7 @@ static void watchdog_overflow_callback(struct perf_event *event, > trigger_allbutself_cpu_backtrace(); > > if (hardlockup_panic) > - panic("Hard LOCKUP"); > + nmi_panic("Hard LOCKUP"); > > __this_cpu_write(hard_watchdog_warn, true); > return; > -- > 2.3.5 > > -- > Regards/Gruss, > Boris. > > ECO tip #101: Trim your mails when you reply. ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
WARNING: multiple messages have this Message-ID (diff)
From: "河合英宏 / KAWAI,HIDEHIRO" <hidehiro.kawai.ez@hitachi.com> To: 'Borislav Petkov' <bp@alien8.de> Cc: "x86@kernel.org" <x86@kernel.org>, "Baoquan He" <bhe@redhat.com>, "Jonathan Corbet" <corbet@lwn.net>, "Peter Zijlstra" <peterz@infradead.org>, "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>, "kexec@lists.infradead.org" <kexec@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "Steven Rostedt" <rostedt@goodmis.org>, "Michal Hocko" <mhocko@kernel.org>, "Ingo Molnar" <mingo@redhat.com>, "Thomas Gleixner" <tglx@linutronix.de>, "Eric W. Biederman" <ebiederm@xmission.com>, "H. Peter Anvin" <hpa@zytor.com>, "平松雅巳 / HIRAMATU,MASAMI" <masami.hiramatsu.pt@hitachi.com>, "Andrew Morton" <akpm@linux-foundation.org>, "Ingo Molnar" <mingo@kernel.org>, "Vivek Goyal" <vgoyal@redhat.com> Subject: RE: Re: [V6 PATCH 1/6] panic/x86: Fix re-entrance problem due to panic on NMI Date: Fri, 11 Dec 2015 00:23:51 +0000 [thread overview] Message-ID: <04EAB7311EE43145B2D3536183D1A84454A50151@GSjpTKYDCembx31.service.hitachi.net> (raw) In-Reply-To: <20151210154136.GA4762@pd.tnic> > From: Borislav Petkov [mailto:bp@alien8.de] [...] > Looks better. > > Did some comments cleanup and nmi_panic() macro reformatting so that it > is more readable and ended up applying this: Thanks a lot! Hidehiro Kawai Hitachi, Ltd. Research & Development Group > --- > From: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> > Date: Thu, 10 Dec 2015 10:46:26 +0900 > Subject: [PATCH] panic, x86: Fix re-entrance problem due to panic on NMI > > If panic on NMI happens just after panic() on the same CPU, panic() is > recursively called. Kernel stalls, as a result, after failing to acquire > panic_lock. > > To avoid this problem, don't call panic() in NMI context if we've > already entered panic(). > > For that, introduce nmi_panic() macro to reduce code duplication. In > the case of panic on NMI, don't return from NMI handlers if another CPU > already panicked. > > Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> > Acked-by: Michal Hocko <mhocko@suse.com> > Cc: Aaron Tomlin <atomlin@redhat.com> > Cc: Andrew Morton <akpm@linux-foundation.org> > Cc: Andy Lutomirski <luto@kernel.org> > Cc: Baoquan He <bhe@redhat.com> > Cc: Chris Metcalf <cmetcalf@ezchip.com> > Cc: David Hildenbrand <dahi@linux.vnet.ibm.com> > Cc: Don Zickus <dzickus@redhat.com> > Cc: "Eric W. Biederman" <ebiederm@xmission.com> > Cc: Frederic Weisbecker <fweisbec@gmail.com> > Cc: Gobinda Charan Maji <gobinda.cemk07@gmail.com> > Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com> > Cc: "H. Peter Anvin" <hpa@zytor.com> > Cc: Ingo Molnar <mingo@kernel.org> > Cc: Javi Merino <javi.merino@arm.com> > Cc: Jonathan Corbet <corbet@lwn.net> > Cc: kexec@lists.infradead.org > Cc: linux-doc@vger.kernel.org > Cc: lkml <linux-kernel@vger.kernel.org> > Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> > Cc: Michal Nazarewicz <mina86@mina86.com> > Cc: Nicolas Iooss <nicolas.iooss_linux@m4x.org> > Cc: Peter Zijlstra <peterz@infradead.org> > Cc: Prarit Bhargava <prarit@redhat.com> > Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk> > Cc: Rusty Russell <rusty@rustcorp.com.au> > Cc: Seth Jennings <sjenning@redhat.com> > Cc: Steven Rostedt <rostedt@goodmis.org> > Cc: Thomas Gleixner <tglx@linutronix.de> > Cc: Ulrich Obergfell <uobergfe@redhat.com> > Cc: Vitaly Kuznetsov <vkuznets@redhat.com> > Cc: Vivek Goyal <vgoyal@redhat.com> > Link: http://lkml.kernel.org/r/20151210014626.25437.13302.stgit@softrs > [ Cleanup comments, fixup formatting. ] > Signed-off-by: Borislav Petkov <bp@suse.de> > --- > arch/x86/kernel/nmi.c | 16 ++++++++++++---- > include/linux/kernel.h | 20 ++++++++++++++++++++ > kernel/panic.c | 16 +++++++++++++--- > kernel/watchdog.c | 2 +- > 4 files changed, 46 insertions(+), 8 deletions(-) > > diff --git a/arch/x86/kernel/nmi.c b/arch/x86/kernel/nmi.c > index 697f90db0e37..292a24bd0553 100644 > --- a/arch/x86/kernel/nmi.c > +++ b/arch/x86/kernel/nmi.c > @@ -231,7 +231,7 @@ pci_serr_error(unsigned char reason, struct pt_regs *regs) > #endif > > if (panic_on_unrecovered_nmi) > - panic("NMI: Not continuing"); > + nmi_panic("NMI: Not continuing"); > > pr_emerg("Dazed and confused, but trying to continue\n"); > > @@ -255,8 +255,16 @@ io_check_error(unsigned char reason, struct pt_regs *regs) > reason, smp_processor_id()); > show_regs(regs); > > - if (panic_on_io_nmi) > - panic("NMI IOCK error: Not continuing"); > + if (panic_on_io_nmi) { > + nmi_panic("NMI IOCK error: Not continuing"); > + > + /* > + * If end up here, it means we have received an NMI while > + * processing panic(). Simply return without delaying and > + * re-enabling NMI. > + */ > + return; > + } > > /* Re-enable the IOCK line, wait for a few seconds */ > reason = (reason & NMI_REASON_CLEAR_MASK) | NMI_REASON_CLEAR_IOCHK; > @@ -297,7 +305,7 @@ unknown_nmi_error(unsigned char reason, struct pt_regs *regs) > > pr_emerg("Do you have a strange power saving mode enabled?\n"); > if (unknown_nmi_panic || panic_on_unrecovered_nmi) > - panic("NMI: Not continuing"); > + nmi_panic("NMI: Not continuing"); > > pr_emerg("Dazed and confused, but trying to continue\n"); > } > diff --git a/include/linux/kernel.h b/include/linux/kernel.h > index 350dfb08aee3..750cc5c7c999 100644 > --- a/include/linux/kernel.h > +++ b/include/linux/kernel.h > @@ -446,6 +446,26 @@ extern int sysctl_panic_on_stackoverflow; > extern bool crash_kexec_post_notifiers; > > /* > + * panic_cpu is used for synchronizing panic() and crash_kexec() execution. It > + * holds a CPU number which is executing panic() currently. A value of > + * PANIC_CPU_INVALID means no CPU has entered panic() or crash_kexec(). > + */ > +extern atomic_t panic_cpu; > +#define PANIC_CPU_INVALID -1 > + > +/* > + * A variant of panic() called from NMI context. We return if we've already > + * panicked on this CPU. > + */ > +#define nmi_panic(fmt, ...) \ > +do { \ > + int cpu = raw_smp_processor_id(); \ > + \ > + if (atomic_cmpxchg(&panic_cpu, PANIC_CPU_INVALID, cpu) != cpu) \ > + panic(fmt, ##__VA_ARGS__); \ > +} while (0) > + > +/* > * Only to be used by arch init code. If the user over-wrote the default > * CONFIG_PANIC_TIMEOUT, honor it. > */ > diff --git a/kernel/panic.c b/kernel/panic.c > index 4b150bc0c6c1..3344524cf6ff 100644 > --- a/kernel/panic.c > +++ b/kernel/panic.c > @@ -61,6 +61,8 @@ void __weak panic_smp_self_stop(void) > cpu_relax(); > } > > +atomic_t panic_cpu = ATOMIC_INIT(PANIC_CPU_INVALID); > + > /** > * panic - halt the system > * @fmt: The text string to print > @@ -71,17 +73,17 @@ void __weak panic_smp_self_stop(void) > */ > void panic(const char *fmt, ...) > { > - static DEFINE_SPINLOCK(panic_lock); > static char buf[1024]; > va_list args; > long i, i_next = 0; > int state = 0; > + int old_cpu, this_cpu; > > /* > * Disable local interrupts. This will prevent panic_smp_self_stop > * from deadlocking the first cpu that invokes the panic, since > * there is nothing to prevent an interrupt handler (that runs > - * after the panic_lock is acquired) from invoking panic again. > + * after setting panic_cpu) from invoking panic() again. > */ > local_irq_disable(); > > @@ -94,8 +96,16 @@ void panic(const char *fmt, ...) > * multiple parallel invocations of panic, all other CPUs either > * stop themself or will wait until they are stopped by the 1st CPU > * with smp_send_stop(). > + * > + * `old_cpu == PANIC_CPU_INVALID' means this is the 1st CPU which > + * comes here, so go ahead. > + * `old_cpu == this_cpu' means we came from nmi_panic() which sets > + * panic_cpu to this CPU. In this case, this is also the 1st CPU. > */ > - if (!spin_trylock(&panic_lock)) > + this_cpu = raw_smp_processor_id(); > + old_cpu = atomic_cmpxchg(&panic_cpu, PANIC_CPU_INVALID, this_cpu); > + > + if (old_cpu != PANIC_CPU_INVALID && old_cpu != this_cpu) > panic_smp_self_stop(); > > console_verbose(); > diff --git a/kernel/watchdog.c b/kernel/watchdog.c > index 18f34cf75f74..b9be18fae154 100644 > --- a/kernel/watchdog.c > +++ b/kernel/watchdog.c > @@ -351,7 +351,7 @@ static void watchdog_overflow_callback(struct perf_event *event, > trigger_allbutself_cpu_backtrace(); > > if (hardlockup_panic) > - panic("Hard LOCKUP"); > + nmi_panic("Hard LOCKUP"); > > __this_cpu_write(hard_watchdog_warn, true); > return; > -- > 2.3.5 > > -- > Regards/Gruss, > Boris. > > ECO tip #101: Trim your mails when you reply. _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-12-11 0:24 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-10 1:46 [V6 PATCH 0/6] Fix race issues among panic, NMI and crash_kexec Hidehiro Kawai 2015-12-10 1:46 ` Hidehiro Kawai 2015-12-10 1:46 ` [V6 PATCH 1/6] panic/x86: Fix re-entrance problem due to panic on NMI Hidehiro Kawai 2015-12-10 1:46 ` Hidehiro Kawai 2015-12-10 15:41 ` Borislav Petkov 2015-12-10 15:41 ` Borislav Petkov 2015-12-11 0:23 ` 河合英宏 / KAWAI,HIDEHIRO [this message] 2015-12-11 0:23 ` 河合英宏 / KAWAI,HIDEHIRO 2015-12-19 10:12 ` [tip:x86/apic] panic, x86: " tip-bot for Hidehiro Kawai 2015-12-10 1:46 ` [V6 PATCH 2/6] panic/x86: Allow CPUs to save registers even if they are looping in NMI context Hidehiro Kawai 2015-12-10 1:46 ` Hidehiro Kawai 2015-12-19 10:13 ` [tip:x86/apic] panic, x86: Allow CPUs to save registers even if " tip-bot for Hidehiro Kawai 2015-12-10 1:46 ` [V6 PATCH 3/6] kexec: Fix race between panic() and crash_kexec() called directly Hidehiro Kawai 2015-12-10 1:46 ` Hidehiro Kawai 2015-12-19 10:13 ` [tip:x86/apic] kexec: Fix race between panic() and crash_kexec() tip-bot for Hidehiro Kawai 2015-12-10 1:46 ` [V6 PATCH 4/6] x86/apic: Introduce apic_extnmi boot option Hidehiro Kawai 2015-12-10 1:46 ` Hidehiro Kawai 2015-12-19 10:13 ` [tip:x86/apic] x86/apic: Introduce apic_extnmi command line parameter tip-bot for Hidehiro Kawai 2015-12-10 1:46 ` [V6 PATCH 5/6] x86/nmi: Fix to save registers for crash dump on external NMI broadcast Hidehiro Kawai 2015-12-10 1:46 ` Hidehiro Kawai 2015-12-10 3:57 ` kbuild test robot 2015-12-10 3:57 ` kbuild test robot 2015-12-10 6:36 ` 河合英宏 / KAWAI,HIDEHIRO 2015-12-10 6:36 ` 河合英宏 / KAWAI,HIDEHIRO 2015-12-10 6:52 ` [V6.1 " Hidehiro Kawai 2015-12-10 6:52 ` Hidehiro Kawai 2015-12-11 18:04 ` Borislav Petkov 2015-12-11 18:04 ` Borislav Petkov 2015-12-19 10:14 ` [tip:x86/apic] x86/nmi: Save regs in crash dump on external NMI tip-bot for Hidehiro Kawai 2015-12-10 1:46 ` [V6 PATCH 6/6] Documentation: Add documentation for kernel.panic_on_io_nmi sysctl Hidehiro Kawai 2015-12-10 1:46 ` Hidehiro Kawai 2015-12-19 10:14 ` [tip:x86/apic] Documentation: Document " tip-bot for Hidehiro Kawai 2015-12-12 11:17 ` [V6 PATCH 0/6] Fix race issues among panic, NMI and crash_kexec Borislav Petkov 2015-12-12 11:17 ` Borislav Petkov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=04EAB7311EE43145B2D3536183D1A84454A50151@GSjpTKYDCembx31.service.hitachi.net \ --to=hidehiro.kawai.ez@hitachi.com \ --cc=akpm@linux-foundation.org \ --cc=bhe@redhat.com \ --cc=bp@alien8.de \ --cc=corbet@lwn.net \ --cc=ebiederm@xmission.com \ --cc=hpa@zytor.com \ --cc=kexec@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=masami.hiramatsu.pt@hitachi.com \ --cc=mhocko@kernel.org \ --cc=mingo@kernel.org \ --cc=mingo@redhat.com \ --cc=peterz@infradead.org \ --cc=rostedt@goodmis.org \ --cc=tglx@linutronix.de \ --cc=vgoyal@redhat.com \ --cc=x86@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.