From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: Greg KH <greg@kroah.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Norberto Bensa <norberto+linux-kernel@bensa.ath.cx>,
linux-kernel@vger.kernel.org
Subject: Re: does udev support sw raid0?
Date: Fri, 14 May 2004 12:10:53 -0700 [thread overview]
Message-ID: <40A519BD.3030000@backtobasicsmgmt.com> (raw)
In-Reply-To: <20040514184659.GA2401@kroah.com>
Greg KH wrote:
> How did this work with devfs then? The device node would not be present
> before the ioctl needed to be called, right? Or did it do the "magic
> lookup" mess and just "know" about md devices?
Right, see my recent thread on linux-hotplug-devel about this very subject.
As it stands today, the only gendisk that md registers without being
asked to do so is md0, so /dev/md0 will always be present on a
udev-enabled system with md. If you have auto-start MD arrays on your
system, then those will be registered as well when md autostarts them at
kernel boot time.
All other arrays (those that you want to start using mdadm, or those
that you want to create because they've never existing before) suffer
from the problem of requiring a device node before they can be controlled.
I chatted with Neil Brown about this, and he would not be opposed to the
md driver exposing a character device specifically for the purpose of
handling the md ioctls (like dm does), but when I looked more into it it
seemed to be a waste of effort; the time could be better spent porting
the md personalities over to dm, where all this stuff already works
properly and there is naming/splitting/partitioning/etc. available.
next prev parent reply other threads:[~2004-05-14 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 17:42 does udev support sw raid0? Norberto Bensa
2004-05-14 18:34 ` Greg KH
2004-05-14 18:39 ` Christoph Hellwig
2004-05-14 18:46 ` Greg KH
2004-05-14 18:51 ` Christoph Hellwig
2004-05-14 19:10 ` Kevin P. Fleming [this message]
2004-05-14 18:50 ` Norberto Bensa
2004-05-14 18:48 ` Norberto Bensa
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=40A519BD.3030000@backtobasicsmgmt.com \
--to=kpfleming@backtobasicsmgmt.com \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=norberto+linux-kernel@bensa.ath.cx \
/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