From: Andrew Morton <akpm@linux-foundation.org>
To: Takenori Nagano <t-nagano@ah.jp.nec.com>
Cc: linux-kernel@vger.kernel.org, vgoyal@in.ibm.com,
"Eric W. Biederman" <ebiederm@xmission.com>,
k-miyoshi@cb.jp.nec.com, kexec@lists.infradead.org,
Bernhard Walle <bwalle@suse.de>, Keith Owens <kaos@ocs.com.au>,
kdb@oss.sgi.com
Subject: Re: [PATCH 0/2] add new notifier function ,take2
Date: Thu, 18 Oct 2007 00:06:51 -0700 [thread overview]
Message-ID: <20071018000651.35b26e42.akpm@linux-foundation.org> (raw)
In-Reply-To: <471700F4.1080200@ah.jp.nec.com>
On Thu, 18 Oct 2007 15:45:08 +0900 Takenori Nagano <t-nagano@ah.jp.nec.com> wrote:
> Hi,
>
> A big thanks to everybody who read and replied to first version. I have tried to
> incorporate reviewer's comments and suggestions.
>
> changelog take1 -> take2
>
> - Rebased 2.6.23
> - comment updated
> - renamed the notifiner name "tunable_notifier" to "tunable_atomic_notifier"
> - fixed typo
>
>
> These patches add new notifier function and implement it to panic_notifier_list.
> We used the hardcoded notifier chain so far, but it was not flexible. New
> notifier is very flexible, because user can change a list of order by debugfs.
>
> Thanks,
>
> Example)
>
> # cd /sys/kernel/debug/
> # ls
> kprobes pktcdvd
> # insmod ipmi_msghandler.ko
> # ls
> kprobes panic_notifier_list pktcdvd
> # cd panic_notifier_list/
> # ls
> ipmi_msghandler
> # insmod ipmi_watchdog.ko
> # ls
> ipmi_msghandler ipmi_wdog
> # cat ipmi_msghandler/priority
> 200
> # cat ipmi_wdog/priority
> 150
> #
> Kernel panic - not syncing: panic
> ipmi_msghandler : notifier calls panic_event().
> ipmi_watchdog : notifier calls wdog_panic_handler().
>
> .....(reboot)
>
> # cat ipmi_msghandler/priority
> 200
> # cat ipmi_wdog/priority
> 150
> # echo 300 > ipmi_wdog/priority
> #
> Kernel panic - not syncing: panic
> ipmi_watchdog : notifier calls wdog_panic_handler().
> ipmi_msghandler : notifier calls panic_event().
I can sort-of see what this is doing. Runtime-definable management of
which notifier functions will be called on a panic? Or maybe I
misunderstood.
But even if I did understand, I don't understand why Linux needs this
feature - what are the use cases, what is the value to our users?
Can you please flesh that information out a bit more?
The patches are somewhat wordwrapped - please check your email client
configuration, thanks.
next prev parent reply other threads:[~2007-10-18 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 6:45 [PATCH 0/2] add new notifier function ,take2 Takenori Nagano
2007-10-18 7:06 ` Andrew Morton [this message]
2007-10-18 8:06 ` Vivek Goyal
2007-10-18 8:52 ` Takenori Nagano
2007-10-21 12:00 ` Nick Piggin
[not found] ` <471D4668.4090300@ah.jp.nec.com>
2007-10-24 6:48 ` sysfs sys/kernel/ namespace (was Re: [PATCH 0/2] add new notifier function ,take2) Nick Piggin
2007-10-24 11:12 ` Kay Sievers
2007-10-25 2:31 ` Nick Piggin
2007-10-25 5:45 ` Greg KH
2007-10-25 6:12 ` Nick Piggin
2007-10-25 6:48 ` [PATCH 0/2] add new notifier function ,take2 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=20071018000651.35b26e42.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=ebiederm@xmission.com \
--cc=k-miyoshi@cb.jp.nec.com \
--cc=kaos@ocs.com.au \
--cc=kdb@oss.sgi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t-nagano@ah.jp.nec.com \
--cc=vgoyal@in.ibm.com \
/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