From: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: Baoquan He <bhe@redhat.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
ebiederm@xmission.com, masami.hiramatsu.pt@hitachi.com,
vgoyal@redhat.com
Subject: Re: [PATCH] kernel/panic/kexec: fix "crash_kexec_post_notifiers" option issue in oops path
Date: Tue, 10 Feb 2015 17:32:17 +0900 [thread overview]
Message-ID: <54D9C211.8010000@hitachi.com> (raw)
In-Reply-To: <20150209032914.GB1847@dhcp-16-105.nay.redhat.com>
Hello,
(2015/02/09 12:29), Baoquan He wrote:> On 02/09/15 at 12:22pm, HATAYAMA Daisuke wrote:
>> From: Baoquan He <bhe@redhat.com>
>>> On 02/05/15 at 05:59pm, HATAYAMA Daisuke wrote:
>>>> diff --git a/kernel/kexec.c b/kernel/kexec.c
>>>> index 9a8a01a..0ecf252 100644
>>>> --- a/kernel/kexec.c
>>>> +++ b/kernel/kexec.c
>>>> @@ -84,6 +84,8 @@ struct resource crashk_low_res = {
>>>>
>>>> int kexec_should_crash(struct task_struct *p)
>>>> {
>>>> + if (crash_kexec_post_notifiers)
>>>> + return 0;
>>>> if (in_interrupt() || !p->pid || is_global_init(p) || panic_on_oops)
>>>> return 1;
>>>
>>> What if these two conditions !p->pid || is_global_init(p) are satisfied?
>>> Seems the behavious is changed.
>>>
>>
>> Please further follow do_exit() path. For each condition, there are
>> the corresponding panic() calls. In summary:
>>
>> oops_end
>> 1) panic() for in_interrupt()
>> 2) panic() for panic_on_oops
>> do_exit
>> 3) panic() for !p->pid (idle task)
>> exit_notify
>> forget_original_parent
>> find_child_reaper
>> 4) panic() for p->pid == 1 (init task)
>
> Yes, all conditions have been covered.
>
> So this patch is necessary, ACK it. Thanks
>
> Acked-by: Baoquan He <bhe@redhat.com>
Thanks for the patch!
I tested it in following cases on x86_64 and it worked well;
my panic notifier was called, then 2nd kernel booted.
- Null pointer dereference in each context of
- hard IRQ
- pid == 0
- pid == 1
- others with panic_on_oops=1
- Zero-divide in the context of normal process
(panic_on_oops=1)
Tested-by: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
--
Hidehiro Kawai
Hitachi, Yokohama Research Laboratory
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-02-10 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 8:59 [PATCH] kernel/panic/kexec: fix "crash_kexec_post_notifiers" option issue in oops path HATAYAMA Daisuke
2015-02-09 2:40 ` Baoquan He
2015-02-09 3:22 ` HATAYAMA Daisuke
2015-02-09 3:29 ` Baoquan He
2015-02-10 8:32 ` Hidehiro Kawai [this message]
2015-02-20 8:31 ` HATAYAMA, Daisuke
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=54D9C211.8010000@hitachi.com \
--to=hidehiro.kawai.ez@hitachi.com \
--cc=bhe@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=vgoyal@redhat.com \
/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