All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <lennart@poettering.net>
To: David Disseldorp <ddiss@suse.de>
Cc: ceph-devel@vger.kernel.org, systemd-devel@lists.freedesktop.org
Subject: Re: [PATCH] rules: block - add dm devices to whitelist
Date: Mon, 10 Jul 2017 11:53:03 +0200	[thread overview]
Message-ID: <20170710095303.GA6261@gardel-login> (raw)
In-Reply-To: <20170710113703.13ca760d@suse.de>

On Mon, 10.07.17 11:37, David Disseldorp (ddiss@suse.de) wrote:

> Thanks for the feedback, Lennart...
> 
> On Mon, 10 Jul 2017 10:38:38 +0200, Lennart Poettering wrote:
> 
> > On Wed, 05.07.17 13:01, David Disseldorp (ddiss@suse.de) wrote:
> > 
> > > Ceph relies on by-partuuid symlinks, in order to locate the journal
> > > partition from a given OSD partition. For details, see
> > > http://tracker.ceph.com/issues/19489.  
> > 
> > This appears way too broad, as it would apply to all LVM and all other
> > devices.
> >
> > It appears to me Ceph should do the same as LVM does for this, and
> > ship its own set of rules, and be careful to only match against the
> > actual devices it creates.
> 
> We can certainly do this in a Ceph specific manner via the existing
> 95-ceph-osd.rules, but my impression was that the by-partuuid symlinks
> are "owned" by 60-persistent-storage.rules .
> 
> If you don't think the existence of these symlinks for dm paths will be
> of use to others then I'll go ahead and propose it as a Ceph only
> change.

Hmmm, so thinking about this again: "partuuid" is actually for GPT
partition UUIDs if I recall recorrectly, they wouldn't be generated
for DM devices anyway, since they are one layer removed from the GPT,
so are you even sure this will do what you are asking for?

But even if this actually works: DM links so far are created by the
LVM/libdevicemapper/ packages, not by udev, and I don't think this
should change. Hence, please talk to the LVM/libdevicemapper folks
about this and ask them for including it.

Lennart

-- 
Lennart Poettering, Red Hat
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

  reply	other threads:[~2017-07-10  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 11:01 [PATCH] rules: block - add dm devices to whitelist David Disseldorp
2017-07-10  8:38 ` Lennart Poettering
2017-07-10  9:37   ` [systemd-devel] " David Disseldorp
2017-07-10  9:53     ` Lennart Poettering [this message]
2017-07-10 10:14       ` Peter Rajnoha
2017-07-10 10:47         ` Peter Rajnoha
2017-07-10 11:18           ` [systemd-devel] " David Disseldorp

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=20170710095303.GA6261@gardel-login \
    --to=lennart@poettering.net \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ddiss@suse.de \
    --cc=systemd-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.