From: Alasdair G Kergon <agk@redhat.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: device-mapper development <dm-devel@redhat.com>,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [dm-devel] [PATCH] improve atomicity of device creation
Date: Tue, 11 Dec 2007 19:13:21 +0000 [thread overview]
Message-ID: <20071211191321.GX22311@agk.fab.redhat.com> (raw)
In-Reply-To: <1197397532.2579.26.camel@lov.site>
On Tue, Dec 11, 2007 at 07:25:32PM +0100, Kay Sievers wrote:
> Should we create an additional new iocl to request the device node
> creation, or add that call to an existing one?
Currently we get an ADD from alloc_dev -> add_disk -> register_disk.
But the device is not usable until the dm resume ioctl, so ideally that
one should be ignored, and it's the CHANGE issued by dm resume that udev
should act upon. (That's not essential though - the /dev node can be
created in response to the ADD, but nothing in udev userspace should
attempt to open it until after the CHANGE is received.)
> Could it be that we want to pass more properties to the event, which are
> added as environment keys?
Don't think so - we'll be handing full control of ownership/permissions
over to udev.
Alasdair
--
agk@redhat.com
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-12-11 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 16:08 [PATCH] improve atomicity of device creation Scott James Remnant
2007-12-11 16:25 ` [dm-devel] " Alasdair G Kergon
2007-12-11 16:42 ` Scott James Remnant
2007-12-11 17:03 ` Alasdair G Kergon
2007-12-11 17:18 ` Scott James Remnant
2007-12-11 17:51 ` Kay Sievers
2007-12-11 18:08 ` Alasdair G Kergon
2007-12-11 18:25 ` Kay Sievers
2007-12-11 19:13 ` Alasdair G Kergon [this message]
2007-12-11 19:43 ` Alasdair G Kergon
2007-12-11 17:35 ` Kay Sievers
2007-12-11 17:40 ` Scott James Remnant
2007-12-11 17:53 ` Alasdair G Kergon
2007-12-11 19:09 ` Scott James Remnant
2007-12-11 18:03 ` Kay Sievers
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=20071211191321.GX22311@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).