From: Andreas Steinmetz <ast@domdv.de>
To: linux-kernel@vger.kernel.org
Subject: reboot notifier priority definitions
Date: Tue, 11 Sep 2001 01:56:34 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20010911015634.ast@domdv.de> (raw)
As a suggestion to prevent further shutdown/reboot notifier processing problems
here's a (crude) attempt of definitions for include/linux/notifier.h. I do
believe it needs to be heavily reworked by someone with a broad kernel overview.
#define NOTIFY_REBOOT_PHYSICAL 0x00 /* scsi */
#define NOTIFY_REBOOT_LOGICAL 0x10 /* md, lvm */
#define NOTIFY_REBOOT_FS 0x20 /* knfsd */
#define NOTIFY_REBOOT_APPLICATION 0x30 /* tux */
The current situation of not having such definitions already did lead to a
kernel oops (md<->scsi). I do fear that if such definitions are not introduced:
1. code maintainers will strictly stick to priority 0 or will use random
and not interoperable priorities
2. more and more interference problems will arise due to the above point
Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
next reply other threads:[~2001-09-10 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-10 23:56 Andreas Steinmetz [this message]
2001-09-11 1:18 ` reboot notifier priority definitions Neil Brown
2001-09-11 1:26 ` Andreas Steinmetz
2001-09-11 5:34 ` Neil Brown
2001-09-11 14:46 ` Alan Cox
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=XFMail.20010911015634.ast@domdv.de \
--to=ast@domdv.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox