linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev lvm permisions
Date: Mon, 15 Dec 2008 19:37:53 +0000	[thread overview]
Message-ID: <20081215193753.GG19917@agk.fab.redhat.com> (raw)
In-Reply-To: <1229336451.19633.4.camel@linux-pqqd.site>

On Mon, Dec 15, 2008 at 07:38:31PM +0100, Kay Sievers wrote:
> In fact, it's good that you started shipping these patches, so it
> shows how stuff should work. And it hopefully puts some pressure on
> the guys who should fix their stuff after all these years. Hint, hint
> to someone in the Cc: list. :)
 
Well let's try to summarise how far we got in those discussions:

1) udev able to query device-mapper to determine what the /dev/mapper
entry should be called.
- udev uses dmsetup.  Sorted.

2) udev able to query device-mapper to determine what the link should be
called.
- udev uses dmsetup, checks for the LVM prefix on the UUID then either
splits the name into components (vgname+lvname+layer) itself (remembering
to unquote doubled hyphens) or calls out to LVM2 to do that.  (There
may be some sequencing issues here.)

3) udev able to determine whether a link needs to exist in /dev/<vgname> or not
- work on the basis that the requirement is having the LVM uuid prefix and
  having no 'layer' in the name.  (This may change when we support internal
  stacking better.)

4) lvm2 able to sleep until udev has completed a particular sequence of async
operations (without second-guessing udev and looking if the right things have
appeared in /dev)
- unresolved.

Alasdair
-- 
agk@redhat.com

  parent reply	other threads:[~2008-12-15 19:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 10:20 udev lvm permisions Geert Geurts
2008-12-15 11:35 ` Michal Soltys
2008-12-15 14:23 ` Michal Soltys
2008-12-15 14:59 ` Kay Sievers
2008-12-15 15:24 ` Geert Geurts
2008-12-15 15:47 ` Kay Sievers
2008-12-15 15:55 ` Scott James Remnant
2008-12-15 16:13 ` Michal Soltys
2008-12-15 17:02 ` David Zeuthen
2008-12-15 17:06 ` Scott James Remnant
2008-12-15 17:12 ` David Zeuthen
2008-12-15 17:14 ` Kay Sievers
2008-12-15 17:18 ` Scott James Remnant
2008-12-15 17:19 ` Kay Sievers
2008-12-15 17:21 ` Geert Geurts
2008-12-15 17:37 ` Kay Sievers
2008-12-15 17:59 ` Scott James Remnant
2008-12-15 18:19 ` Kay Sievers
2008-12-15 18:21 ` Scott James Remnant
2008-12-15 18:38 ` Kay Sievers
2008-12-15 19:37 ` Alasdair G Kergon [this message]
2008-12-15 19:51 ` [lvm-devel] " Alasdair G Kergon
2008-12-15 20:14 ` David Zeuthen
2008-12-15 20:29 ` Alasdair G Kergon

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=20081215193753.GG19917@agk.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).