From: "long.wanglong" <long.wanglong@huawei.com>
To: Petr Mladek <pmladek@suse.cz>
Cc: <rostedt@goodmis.org>, <jkosina@suse.cz>,
<gregkh@linuxfoundation.org>, <stable@vger.kernel.org>,
<wanglong@laoqinren.net>, <peifeiyue@huawei.com>,
<linux-kernel@vger.kernel.org>, <morgan.wang@huawei.com>,
<paulmck@linux.vnet.ibm.com>, <dzickus@redhat.com>,
<x86@kernel.org>, <sasha.levin@oracle.com>
Subject: Re: [RFC PATCH 16/17] x86/nmi: Perform a safe NMI stack trace on all CPUs
Date: Tue, 19 May 2015 16:56:03 +0800 [thread overview]
Message-ID: <555AFAA3.5070906@huawei.com> (raw)
In-Reply-To: <20150518141748.GE2632@pathway.suse.cz>
On 2015/5/18 22:17, Petr Mladek wrote:
> On Thu 2015-05-14 11:35:03, Wang Long wrote:
>> From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
>>
>> commit a9edc88093287183ac934be44f295f183b2c62dd upstream.
>>
>> 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 avoid this, when the NMI triggers, it switches the printk
>> routine for that CPU to call a NMI safe printk function that records the
>> printk in a per_cpu seq_buf descriptor. After all NMIs have finished
>> recording its data, the seq_bufs are printed in a safe context.
>>
>> Link: http://lkml.kernel.org/p/20140619213952.360076309@goodmis.org
>> Link: http://lkml.kernel.org/r/20141115050605.055232587@goodmis.org
>>
>> Tested-by: Jiri Kosina <jkosina@suse.cz>
>> Acked-by: Jiri Kosina <jkosina@suse.cz>
>> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>> Reviewed-by: Petr Mladek <pmladek@suse.cz>
>> [wanglong: backport to 3.10 stable
>> - adjust context
>> ]
>> Signed-off-by: Wang Long <long.wanglong@huawei.com>
>> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>> ---
>> arch/x86/kernel/apic/hw_nmi.c | 86 +++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 83 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/x86/kernel/apic/hw_nmi.c b/arch/x86/kernel/apic/hw_nmi.c
>> index a698d71..1eb5f90 100644
>> --- a/arch/x86/kernel/apic/hw_nmi.c
>> +++ b/arch/x86/kernel/apic/hw_nmi.c
>> @@ -18,6 +18,7 @@
>> #include <linux/nmi.h>
>> #include <linux/module.h>
>> #include <linux/delay.h>
>> +#include <linux/seq_buf.h>
>>
>> #ifdef CONFIG_HARDLOCKUP_DETECTOR
>> u64 hw_nmi_get_sample_period(int watchdog_thresh)
>> @@ -29,12 +30,33 @@ u64 hw_nmi_get_sample_period(int watchdog_thresh)
>> #ifdef arch_trigger_all_cpu_backtrace
>> /* For reliability, we're prepared to waste bits here. */
>> static DECLARE_BITMAP(backtrace_mask, NR_CPUS) __read_mostly;
>> +static cpumask_var_t printtrace_mask;
>> +
>> +#define NMI_BUF_SIZE 4096
>
> Please, replace spaces with tabs.
>
> In fact, the indentation is broken in this whole patch.
>
> The content looks fine, though.
>
> Best Regards,
> Petr
>
Hi Petr,
Thank you for your review. Sorry for the indentation broken.
I will send the patch v2.
Best Regards
Wang Long
next prev parent reply other threads:[~2015-05-19 8:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 11:34 [RFC PATCH 00/17][request for stable 3.10 inclusion] x86/nmi: Print all cpu stacks from NMI safely Wang Long
2015-05-14 11:34 ` [RFC PATCH 01/17] tracing: Create seq_buf layer in trace_seq Wang Long
2015-05-14 11:34 ` [RFC PATCH 02/17] tracing: Convert seq_buf_path() to be like seq_path() Wang Long
2015-05-14 11:34 ` [RFC PATCH 03/17] tracing: Convert seq_buf fields to be like seq_file fields Wang Long
2015-05-14 11:34 ` [RFC PATCH 04/17] tracing: Add a seq_buf_clear() helper and clear len and readpos in init Wang Long
2015-05-14 11:34 ` [RFC PATCH 05/17] seq_buf: Create seq_buf_used() to find out how much was written Wang Long
2015-05-14 11:34 ` [RFC PATCH 06/17] tracing: Use trace_seq_used() and seq_buf_used() instead of len Wang Long
2015-05-14 11:34 ` [RFC PATCH 07/17] seq_buf: Add seq_buf_can_fit() helper function Wang Long
2015-05-14 11:34 ` [RFC PATCH 08/17] tracing: Have seq_buf use full buffer Wang Long
2015-05-14 11:34 ` [RFC PATCH 09/17] tracing: Add seq_buf_get_buf() and seq_buf_commit() helper functions Wang Long
2015-05-14 11:34 ` [RFC PATCH 10/17] seq-buf: Make seq_buf_bprintf() conditional on CONFIG_BINARY_PRINTF Wang Long
2015-05-14 11:34 ` [RFC PATCH 11/17] seq_buf: Move the seq_buf code to lib/ Wang Long
2015-05-14 11:34 ` [RFC PATCH 12/17] seq_buf: Fix seq_buf_vprintf() truncation Wang Long
2015-05-14 11:35 ` [RFC PATCH 13/17] seq_buf: Fix seq_buf_bprintf() truncation Wang Long
2015-05-14 11:35 ` [RFC PATCH 14/17] printk: Add per_cpu printk func to allow printk to be diverted Wang Long
2015-05-18 13:56 ` Petr Mladek
2015-05-14 11:35 ` [RFC PATCH 15/17] printk/percpu: Define printk_func when printk is not defined Wang Long
2015-05-14 11:35 ` [RFC PATCH 16/17] x86/nmi: Perform a safe NMI stack trace on all CPUs Wang Long
2015-05-18 14:17 ` Petr Mladek
2015-05-19 8:56 ` long.wanglong [this message]
2015-05-14 11:35 ` [RFC PATCH 17/17] x86/nmi: Fix use of unallocated cpumask_var_t Wang Long
2015-05-14 13:55 ` [RFC PATCH 00/17][request for stable 3.10 inclusion] x86/nmi: Print all cpu stacks from NMI safely Steven Rostedt
2015-05-18 3:52 ` long.wanglong
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=555AFAA3.5070906@huawei.com \
--to=long.wanglong@huawei.com \
--cc=dzickus@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan.wang@huawei.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peifeiyue@huawei.com \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=wanglong@laoqinren.net \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).