[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20101019173303.A205.A69D9226@jp.fujitsu.com>
Date: Tue, 19 Oct 2010 17:52:34 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Seiji Aguchi <seiji.aguchi@....com>
Cc: kosaki.motohiro@...fujitsu.com,
"simon.kagstrom@...insight.net" <simon.kagstrom@...insight.net>,
"David.Woodhouse@...el.com" <David.Woodhouse@...el.com>,
"anders.grafstrom@...insight.net" <anders.grafstrom@...insight.net>,
"Artem.Bityutskiy@...ia.com" <Artem.Bityutskiy@...ia.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"jason.wessel@...driver.com" <jason.wessel@...driver.com>,
"jslaby@...e.cz" <jslaby@...e.cz>,
"jmorris@...ei.org" <jmorris@...ei.org>,
"eparis@...hat.com" <eparis@...hat.com>, "hch@....de" <hch@....de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dle-develop@...ts.sourceforge.net"
<dle-develop@...ts.sourceforge.net>,
Satoru Moriya <satoru.moriya@....com>
Subject: Re: [RFC][Patch] Adding kmsg_dump() to reboot/halt/poweroff/emergency_restart path
> 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().
But if they ack this one, I have no objection.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists