From: Artem Bityutskiy <dedekind1@gmail.com>
To: Simon Kagstrom <simon.kagstrom@netinsight.net>
Cc: David VomLehn <dvomlehn@cisco.com>,
Marco Stornelli <marco.stornelli@gmail.com>,
linux-embedded@vger.kernel.org, akpm@linux-foundation.org,
dwmw2@infradead.org, linux-kernel@vger.kernel.org,
mpm@selenic.com, paul.gortmaker@windriver.com,
"Shargorodsky Atal (EXT-Teleca/Helsinki)"
<ext-atal.shargorodsky@nokia.com>
Subject: Re: [PATCH, RFC] panic-note: Annotation from user space for panics
Date: Fri, 13 Nov 2009 16:16:53 +0200 [thread overview]
Message-ID: <1258121813.21596.1229.camel@localhost> (raw)
In-Reply-To: <20091113125946.5353164c@marrow.netinsight.se>
On Fri, 2009-11-13 at 12:59 +0100, Simon Kagstrom wrote:
> (Also fix David Woodhouses address and add Atal)
>
> On Fri, 13 Nov 2009 13:45:48 +0200
> Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
> > So we really need to print some user-space supplied information during
> > the panic, and then we store it on flash with mtdoops, and the later,
> > when the device has network access we send whole bunch of oopses via the
> > network.
>
> Yes, I see that your case would have to be handled differently. A
> complication (which I believe was discussed before) is that kmsg_dump()
> is done before the panic notifiers are called.
>
> The reason I put it there is to have it before crash_kexec(), so I
> guess we'll have to take up the discussion on what to do with it. For
> me it now seems like it would be OK to move kmsg_dump() down below the
> panic notifiers.
>
> If you have a kdump kernel to load, then you will most likely not need
> the kmsg dumped data anyway.
Yeah, I think this is a separate issue which can be fixed separately.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-11-13 14:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 2:13 [PATCH, RFC] panic-note: Annotation from user space for panics David VomLehn
2009-11-12 18:00 ` Marco Stornelli
2009-11-12 21:56 ` David VomLehn
2009-11-13 8:10 ` Simon Kagstrom
2009-11-13 11:45 ` Artem Bityutskiy
2009-11-13 11:59 ` Simon Kagstrom
2009-11-13 14:16 ` Artem Bityutskiy [this message]
2009-11-14 8:28 ` Marco Stornelli
2009-11-17 8:53 ` Artem Bityutskiy
2009-11-17 12:45 ` Marco Stornelli
2009-11-17 13:10 ` Artem Bityutskiy
2009-11-17 15:45 ` Eric W. Biederman
2009-11-17 23:56 ` David VomLehn
2009-11-18 0:28 ` Eric W. Biederman
2009-11-18 0:53 ` David VomLehn
2009-11-18 9:01 ` Américo Wang
2009-11-18 17:01 ` Eric W. Biederman
2009-11-18 0:56 ` Matt Mackall
2009-11-18 16:07 ` Eric W. Biederman
2009-11-18 17:52 ` Tim Bird
2009-11-18 18:16 ` Eric W. Biederman
2009-11-18 18:16 ` Eric W. Biederman
2009-11-18 8:26 ` Artem Bityutskiy
2009-11-17 17:53 ` Marco Stornelli
2009-11-12 18:06 ` Matt Mackall
2009-11-12 21:58 ` David VomLehn
2009-11-13 11:35 ` Artem Bityutskiy
2009-11-12 19:50 ` Paul Gortmaker
2009-11-12 22:09 ` David VomLehn
2009-11-13 11:50 ` Shargorodsky Atal (EXT-Teleca/Helsinki)
2009-11-13 11:26 ` Artem Bityutskiy
2009-11-17 9:03 ` 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=1258121813.21596.1229.camel@localhost \
--to=dedekind1@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvomlehn@cisco.com \
--cc=dwmw2@infradead.org \
--cc=ext-atal.shargorodsky@nokia.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=mpm@selenic.com \
--cc=paul.gortmaker@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.