From: ebiederm@xmission.com (Eric W. Biederman)
To: Ingo Molnar <mingo@kernel.org>
Cc: "Masami Hiramatsu" <masami.hiramatsu.pt@hitachi.com>,
"Baoquan He" <bhe@redhat.com>,
"Hatayama, Daisuke/畑山 大輔" <d.hatayama@jp.fujitsu.com>,
"Vivek Goyal" <vgoyal@redhat.com>,
hidehiro.kawai.ez@hitachi.com, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, akpm@linux-foundation.org,
mingo@redhat.com, bp@suse.de
Subject: Re: [PATCH v2] kernel/panic/kexec: fix "crash_kexec_post_notifiers" option issue in oops path
Date: Tue, 24 Mar 2015 05:27:10 -0500 [thread overview]
Message-ID: <87619qzo5d.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20150324071129.GA28619@gmail.com> (Ingo Molnar's message of "Tue, 24 Mar 2015 08:11:29 +0100")
Ingo Molnar <mingo@kernel.org> writes:
> * Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:
>
>> >
>> > f06e5153f4ae ("kernel/panic.c: add "crash_kexec_post_notifiers" option for kdump after panic_notifers")
>> >
>> > Was that crash_kexec() was called unconditionally after notifiers were
>> > called, which should be fixed via the simple patch below (untested).
>> > Looks much simpler than your fix.
>>
>> No, Daisuke's patch is not for that case. [...]
>
> Yet the actual bug is in that commit, 'crash_kexec_post_notifiers' was
> clearly not a no-op in the default case, against expectations.
>
> So the first step should be to restore the original behavior (my
> patch), then should any new tweaks be added.
Honestly I think the proper fix is to simply revert f06e5153f4ae.
It was clearly not properly tested by the people who wanted it because
they came back quite a while later with additional bleh.
I think this pretty much counts as hitting the code doesn't work let's
remove it threshold.
Eric
next prev parent reply other threads:[~2015-03-24 10:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 16:31 "Hatayama, Daisuke/畑山 大輔"
2015-03-06 18:08 ` Vivek Goyal
2015-03-23 3:47 ` Baoquan He
2015-03-23 7:19 ` Ingo Molnar
2015-03-23 13:37 ` Vivek Goyal
2015-03-23 13:50 ` Ingo Molnar
2015-03-23 14:31 ` Vivek Goyal
2015-03-23 16:01 ` Don Zickus
2015-03-24 3:58 ` Masami Hiramatsu
2015-03-23 15:36 ` Vivek Goyal
2015-03-24 3:30 ` Masami Hiramatsu
2015-03-24 7:11 ` Ingo Molnar
2015-03-24 10:27 ` Eric W. Biederman [this message]
2015-03-24 14:32 ` Vivek Goyal
2015-03-25 15:07 ` Hidehiro Kawai
2015-03-24 14:46 ` Vivek Goyal
2015-03-24 16:18 ` Ingo Molnar
2015-03-24 17:04 ` Vivek Goyal
2015-05-12 8:43 ` Hidehiro Kawai
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=87619qzo5d.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@suse.de \
--cc=d.hatayama@jp.fujitsu.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.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
Powered by JetHome