From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] add kdump_after_notifier
Date: Thu, 26 Jul 2007 18:14:31 +0200 [thread overview]
Message-ID: <20070726161431.GA32008@suse.de> (raw)
In-Reply-To: <20070726155444.GC15969@in.ibm.com>
* Vivek Goyal <vgoyal@in.ibm.com> [2007-07-26 17:54]:
>
> That's true. Its not mainline. We had similar discussion in the past
> also. I think we should allow only audited code to be run after panic().
> Leaving it open to modules or unaudited code makes this solution
> something like LKCD where whole lot of code used to run after the crash,
> hence was unreliable.
>
> If KDB goes mainline, then I think it is not a bad idea to call debugger
> first (if it is enabled) and then one can trigger crash dump from inside
> the debugger.
Well, after thinking again about this, I think the best solution would
to call kdump from KDB with a command as it was done by LKCD. The new
sysctl is too specific ...
Thanks,
Bernhard
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] add kdump_after_notifier
Date: Thu, 26 Jul 2007 18:14:31 +0200 [thread overview]
Message-ID: <20070726161431.GA32008@suse.de> (raw)
In-Reply-To: <20070726155444.GC15969@in.ibm.com>
* Vivek Goyal <vgoyal@in.ibm.com> [2007-07-26 17:54]:
>
> That's true. Its not mainline. We had similar discussion in the past
> also. I think we should allow only audited code to be run after panic().
> Leaving it open to modules or unaudited code makes this solution
> something like LKCD where whole lot of code used to run after the crash,
> hence was unreliable.
>
> If KDB goes mainline, then I think it is not a bad idea to call debugger
> first (if it is enabled) and then one can trigger crash dump from inside
> the debugger.
Well, after thinking again about this, I think the best solution would
to call kdump from KDB with a command as it was done by LKCD. The new
sysctl is too specific ...
Thanks,
Bernhard
next prev parent reply other threads:[~2007-07-26 16:14 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 12:15 [patch] add kdump_after_notifier Takenori Nagano
2007-07-19 12:15 ` Takenori Nagano
2007-07-26 14:07 ` Bernhard Walle
2007-07-26 14:07 ` Bernhard Walle
2007-07-26 15:32 ` Vivek Goyal
2007-07-26 15:32 ` Vivek Goyal
2007-07-26 15:34 ` Bernhard Walle
2007-07-26 15:34 ` Bernhard Walle
2007-07-26 15:44 ` Vivek Goyal
2007-07-26 15:44 ` Vivek Goyal
2007-07-26 15:47 ` Bernhard Walle
2007-07-26 15:47 ` Bernhard Walle
2007-07-26 15:54 ` Vivek Goyal
2007-07-26 15:54 ` Vivek Goyal
2007-07-26 16:14 ` Bernhard Walle [this message]
2007-07-26 16:14 ` Bernhard Walle
2007-07-26 16:21 ` Bernhard Walle
2007-07-26 16:21 ` Bernhard Walle
2007-07-26 23:28 ` Takenori Nagano
2007-07-26 23:28 ` Takenori Nagano
2007-07-30 9:16 ` Vivek Goyal
2007-07-30 9:16 ` Vivek Goyal
2007-07-30 13:42 ` Eric W. Biederman
2007-07-30 13:42 ` Eric W. Biederman
2007-07-31 5:55 ` Takenori Nagano
2007-07-31 5:55 ` Takenori Nagano
2007-07-31 6:53 ` Eric W. Biederman
2007-07-31 6:53 ` Eric W. Biederman
2007-08-01 9:26 ` Takenori Nagano
2007-08-01 9:26 ` Takenori Nagano
2007-08-01 10:00 ` Eric W. Biederman
2007-08-01 10:00 ` Eric W. Biederman
2007-08-02 8:11 ` Takenori Nagano
2007-08-02 8:11 ` Takenori Nagano
2007-08-02 11:28 ` Vivek Goyal
2007-08-02 11:28 ` Vivek Goyal
2007-08-03 4:05 ` Keith Owens
2007-08-03 4:05 ` Keith Owens
2007-08-03 6:25 ` Andrew Morton
2007-08-03 6:25 ` Andrew Morton
2007-08-03 6:34 ` Keith Owens
2007-08-03 6:34 ` Keith Owens
2007-08-03 7:37 ` Andrew Morton
2007-08-03 7:37 ` Andrew Morton
2007-08-03 7:10 ` Eric W. Biederman
2007-08-03 7:10 ` Eric W. Biederman
2007-08-05 11:07 ` Vivek Goyal
2007-08-05 11:07 ` Vivek Goyal
2007-08-14 8:34 ` Takenori Nagano
2007-08-14 8:34 ` Takenori Nagano
2007-08-14 8:37 ` Bernhard Walle
2007-08-14 8:37 ` Bernhard Walle
2007-08-14 8:48 ` Takenori Nagano
2007-08-14 8:48 ` Takenori Nagano
2007-08-14 8:53 ` Bernhard Walle
2007-08-14 8:53 ` Bernhard Walle
2007-08-14 13:24 ` Vivek Goyal
2007-08-14 13:24 ` Vivek Goyal
2007-08-16 9:26 ` Takenori Nagano
2007-08-16 9:26 ` Takenori Nagano
2007-08-16 9:45 ` Bernhard Walle
2007-08-16 9:45 ` Bernhard Walle
2007-08-17 10:56 ` Vivek Goyal
2007-08-17 10:56 ` Vivek Goyal
2007-08-21 7:45 ` Takenori Nagano
2007-08-21 7:45 ` Takenori Nagano
2007-08-23 3:52 ` Vivek Goyal
2007-08-23 3:52 ` Vivek Goyal
2007-08-21 13:18 ` Jay Lan
2007-08-21 13:18 ` Jay Lan
2007-08-21 13:21 ` Bernhard Walle
2007-08-21 13:21 ` Bernhard Walle
2007-08-23 3:56 ` Vivek Goyal
2007-08-23 3:56 ` Vivek Goyal
2007-08-23 17:34 ` Jay Lan
2007-08-23 17:34 ` Jay Lan
2007-10-04 11:30 ` Takenori Nagano
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=20070726161431.GA32008@suse.de \
--to=bwalle@suse.de \
--cc=akpm@linux-foundation.org \
--cc=kexec@lists.infradead.org \
--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 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.