From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: ext KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Seiji Aguchi <seiji.aguchi@hds.com>,
"simon.kagstrom@netinsight.net" <simon.kagstrom@netinsight.net>,
"David.Woodhouse@intel.com" <David.Woodhouse@intel.com>,
"anders.grafstrom@netinsight.net"
<anders.grafstrom@netinsight.net>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"jason.wessel@windriver.com" <jason.wessel@windriver.com>,
"jslaby@suse.cz" <jslaby@suse.cz>,
"jmorris@namei.org" <jmorris@namei.org>,
"eparis@redhat.com" <eparis@redhat.com>,
"hch@lst.de" <hch@lst.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [RFC][Patch] Adding kmsg_dump() to reboot/halt/poweroff/emergency_restart path
Date: Tue, 19 Oct 2010 11:51:12 +0300 [thread overview]
Message-ID: <1287478272.9272.9.camel@localhost> (raw)
In-Reply-To: <20101019173303.A205.A69D9226@jp.fujitsu.com>
On Tue, 2010-10-19 at 10:52 +0200, ext KOSAKI Motohiro wrote:
> > Hi,
> >
> > Final messages from reboot, halt and poweroff aren't output to disk because klogd/syslogd
> > has been killed and root file system has been turned read-only.
> >
> > Final messages from emergency_restart aren't output to disk as well because system may
> > reboot before klogd/syslogd outputs messages to disk.
> >
> > Therefore, it is better to put kmsg_dumper in reboot/halt/poweroff/emergency_restart path.
> > Any comments/advices are welcome.
>
> I think mtdoops user don't want to dump logs if a system reboot/poweroff
> safely because mtd device have write count limitation. and they are main
> user of kmsg_dump().
Right, at least this is how we use mtdoops - we log crashes.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-10-19 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 22:24 [RFC][Patch] Adding kmsg_dump() to reboot/halt/poweroff/emergency_restart path Seiji Aguchi
2010-10-18 22:33 ` Andrew Morton
2010-10-27 19:44 ` Seiji Aguchi
2010-11-03 21:50 ` Aaron Durbin
2010-11-04 7:20 ` Artem Bityutskiy
2010-10-19 8:52 ` KOSAKI Motohiro
2010-10-19 8:51 ` Artem Bityutskiy [this message]
2010-10-27 23:35 ` Andrew Morton
2010-10-28 19:58 ` Artem Bityutskiy
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=1287478272.9272.9.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=David.Woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=anders.grafstrom@netinsight.net \
--cc=dle-develop@lists.sourceforge.net \
--cc=eparis@redhat.com \
--cc=hch@lst.de \
--cc=jason.wessel@windriver.com \
--cc=jmorris@namei.org \
--cc=jslaby@suse.cz \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=simon.kagstrom@netinsight.net \
/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