On Fri, 27 Jun 2014 16:32:46 +0200
Petr Mládek wrote:
> > +/*
> > + * It is not safe to call printk() directly from NMI handlers.
> > + * It may be fine if the NMI detected a lock up and we have no choice
> > + * but to do so, but doing a NMI on all other CPUs to get a back trace
> > + * can be
On Thu 2014-06-26 17:49:06, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> When trigger_all_cpu_backtrace() is called on x86, it will trigger an
> NMI on each CPU and call show_regs(). But this can lead to a hard lock
> up if the NMI comes in on another printk().
>
> In order to av
This patch got rejected by lkml:
>>> linux-kernel@vger.kernel.org (reading confirmation): 550 5.7.1
>>> Content-Policy reject msg: Wrong MIME labeling on 8-bit character texts.
>>> BF:; S1751405AbaFZWBb
I guess quilt couldn't handle Petr's last name (I changed it to 'a'
here).
-- Steve
On
3 matches
Mail list logo
