All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: lvm-devel@redhat.com
Subject: [PATCH 0/2] LVM2: fix lvmetad udev rules for CHANGE events
Date: Fri, 02 Feb 2018 11:55:47 +0100	[thread overview]
Message-ID: <1517568947.4013.17.camel@suse.com> (raw)
In-Reply-To: <1516050733.5699.48.camel@suse.com>

On Mon, 2018-01-15 at 22:12 +0100, Martin Wilck wrote:
> Dear LVM2 maintainers,
> 
> On Thu, 2017-12-21 at 12:57 +0100, Martin Wilck wrote:
> > The current logic in 69-dm-lvm-metad.rules is broken for the
> > default
> > "enable-udev-systemd-background-jobs" case. Detailed information
> > about the
> > problem can be found in the commit message of the 2nd patch in the
> > set.
> > That patch also contains the tiny actual change of this patch set:
> > if
> > systemd
> > background jobs are active, the variables SYSTEMD_ALIAS and
> > SYSTEMD_WANTS are
> > also set for CHANGE events, not only for ADD.
> > 
> > The reason that the patch set is quite large nonetheless is that I
> > wanted
> > the comments in the rules file to match the actual behavior.
> > Substitution of
> > multi-line comments is very hard, if not impossible, with the
> > string
> > substitution approach in the current Makefile. That necessitates
> > the
> > first
> > patch, which introduces no functional change.
> > 
> > Martin Wilck (2):
> >   lvm2: 69-dm-lvm-metad.rules: explicit pvscan rule
> >   lvm2: 69-dm-lvm-metad.rules: set systemd vars on "change"
> > 
> >  udev/69-dm-lvm-metad.rules.in | 53
> > +++++++++++++++++++++++++++++++++++++++----
> >  udev/Makefile.in              |  9 +++++---
> >  2 files changed, 54 insertions(+), 8 deletions(-)
> 
> A review of this patch would be highly appreciated.
> 

a gentle reminder, could someone please have a look?

Regards,
Martin


-- 
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)



      parent reply	other threads:[~2018-02-02 10:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 11:57 [PATCH 0/2] LVM2: fix lvmetad udev rules for CHANGE events Martin Wilck
2017-12-21 11:57 ` [PATCH 1/2] lvm2: 69-dm-lvm-metad.rules: explicit pvscan rule Martin Wilck
2017-12-21 11:57 ` [PATCH 2/2] lvm2: 69-dm-lvm-metad.rules: set systemd vars on "change" Martin Wilck
2018-02-02 14:56   ` Eric Ren
2017-12-22 11:54 ` [PATCH 0/2] LVM2: fix lvmetad udev rules for CHANGE events Martin Wilck
2017-12-27  8:03   ` Eric Ren
2017-12-27  8:48     ` Eric Ren
2017-12-28  2:42       ` Eric Ren
     [not found] ` <1516050733.5699.48.camel@suse.com>
2018-02-02 10:55   ` Martin Wilck [this message]

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=1517568947.4013.17.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=lvm-devel@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 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.