mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Anders Grafstrom <anders.grafstrom@netinsight.net>,
	Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	kosaki.motohiro@jp.fujitsu.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: mtdoops: mtdoops works with kexec correctly
Date: Mon, 21 Dec 2009 15:33:41 +0100	[thread overview]
Message-ID: <20091221153341.2bece1d3@marrow.netinsight.se> (raw)
In-Reply-To: <20091221191254.089E.A69D9226@jp.fujitsu.com>

On Mon, 21 Dec 2009 19:20:35 +0900 (JST)
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:

> commit 2e386e4ba(mtdoops: refactor as a kmsg_dumper) is very good patch.
> but unfortunately it doesn't works with kexec and few embedded user need
> to use kexec. there is no reason to don't implement it. it isn't so
> hard.
> 
> FAQ
> ---
>  Q. Why KMSG_DUMP_OOPS is insufficient?
>  A. Because crash_kexec() is called before KMSG_DUMP_OOPS if
>     panic_on_oops==1.
> 
>  Q. Why do you move KMSG_DUMP_PANIC call place?
>  A. Otherwise kmsg_dump() is called twice if kexec enabled.
>     it's annoy.

I think it would be better to describe these comments in text instead
of as FAQs. Because of the --- it's also removed from the git log.
Maybe something like

	kmsg_dump: Dump on crash_kexec as well

	crash_kexec gets called before kmsg_dump(KMSG_DUMP_OOPS) if
	panic_on_oops is set, so the kernel log buffer is not stored
	for this case.

	This patch adds a KMSG_DUMP_KEXEC dump type which gets called
	when crash_kexec() is invoked. To avoid getting double dumps,
	the old KMSG_DUMP_PANIC is moved below crash_kexec(). The
	mtdoops driver is modified to handle KMSG_DUMP_KEXEC in the
	same way as a panic.


Other than that, it looks fine to me. I've done basic testing against
2.6.33-rc1, but unfortunately without kexec support.

Acked-by: Simon Kagstrom <simon.kagstrom@netinsight.net>

// Simon


  reply	other threads:[~2009-12-21 14:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 10:20 KOSAKI Motohiro
2009-12-21 14:33 ` Simon Kagstrom [this message]
2009-12-22  0:03   ` KOSAKI Motohiro
2009-12-22  3:15     ` [PATCH v2] kmsg_dump: Dump on crash_kexec as well KOSAKI Motohiro

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=20091221153341.2bece1d3@marrow.netinsight.se \
    --to=simon.kagstrom@netinsight.net \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=David.Woodhouse@intel.com \
    --cc=anders.grafstrom@netinsight.net \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®