From: Martin Wilck <mwilck@suse.com>
To: NeilBrown <neilb@suse.de>, Peter Rajnoha <prajnoha@redhat.com>
Cc: Jes Sorensen <jsorensen@fb.com>, Coly Li <colyli@suse.com>,
lvm-devel@redhat.com, linux-raid@vger.kernel.org,
dm-devel@redhat.com, Heming Zhao <heming.zhao@suse.com>
Subject: Re: [PATCH] udev-md-raid-assembly.rules: skip if DM_UDEV_DISABLE_OTHER_RULES_FLAG
Date: Tue, 22 Feb 2022 14:54:33 +0100 [thread overview]
Message-ID: <4b61ca1eafb35e3fdfbc9bb260dc89d56d181499.camel@suse.com> (raw)
In-Reply-To: <164548656531.8827.3365536065813085321@noble.neil.brown.name>
Neil,
On Tue, 2022-02-22 at 10:36 +1100, NeilBrown wrote:
>
> > The flags that DM use for udev were introduced before systemd
> > project
> > even existed. We needed to introduce the
> > DM_UDEV_DISABLE_OTHER_RULES_FLAG
> > to have a possibility for all the "other" (non-dm) udev rules to
> > check
> > for if there's another subsystem stacking its own devices on top of
> > DM
> > ones.
>
> If this is an established API that DM uses, then presumably it is
> documented somewhere. If a link to that documentation were provided,
> it
> would look a a whole lot less like a hack.
Peter has provided a link to libdevmapper.h in his previous post in
this thread. Is this a request for me to include that link in the patch
description?
Regards,
Martin
next prev parent reply other threads:[~2022-02-22 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 20:59 [PATCH] udev-md-raid-assembly.rules: skip if DM_UDEV_DISABLE_OTHER_RULES_FLAG mwilck
2022-02-16 22:09 ` NeilBrown
2022-02-17 10:58 ` Martin Wilck
2022-02-17 13:09 ` Peter Rajnoha
2022-02-21 23:36 ` NeilBrown
2022-02-22 13:54 ` Martin Wilck [this message]
2022-02-22 22:49 ` NeilBrown
2022-02-23 9:47 ` Martin Wilck
2022-02-28 8:48 ` Martin Wilck
2022-03-18 22:42 ` Martin Wilck
2022-02-28 15:28 ` [dm-devel] " Xiao Ni
2022-03-01 7:53 ` Peter Rajnoha
2022-02-17 13:20 ` Peter Rajnoha
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=4b61ca1eafb35e3fdfbc9bb260dc89d56d181499.camel@suse.com \
--to=mwilck@suse.com \
--cc=colyli@suse.com \
--cc=dm-devel@redhat.com \
--cc=heming.zhao@suse.com \
--cc=jsorensen@fb.com \
--cc=linux-raid@vger.kernel.org \
--cc=lvm-devel@redhat.com \
--cc=neilb@suse.de \
--cc=prajnoha@redhat.com \
/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