[dm-devel] [PATCH 2/2] multipath.conf.5: clarify property whitelist handling

Martin Wilck mwilck at suse.com
Mon May 28 12:30:27 UTC 2018


On Wed, 2018-05-16 at 17:43 -0500, Benjamin Marzinski wrote:
> Signed-off-by: Benjamin Marzinski <bmarzins at redhat.com>
> ---
>  multipath/multipath.conf.5 | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/multipath/multipath.conf.5 b/multipath/multipath.conf.5
> index f689795..96d1b66 100644
> --- a/multipath/multipath.conf.5
> +++ b/multipath/multipath.conf.5
> @@ -1181,10 +1181,9 @@ and
>  keywords. For a full description of these keywords please see the
> \fIdevices\fR
>  section description.
>  .LP
> -The \fIproperty\fR blacklist and whitelist handling is different
> from the usual
> -handling in the sense that the whitelist \fIhas\fR to be set,
> otherwise the
> -device will be blacklisted. In these cases the message
> \fIblacklisted, udev
> -property missing\fR will be displayed.
> +The \fIproperty\fR whitelist handling is different from the usual
> +handling in the sense that the device \fIhas\fR to have a udev
> property that
> +matches the whitelist, otherwise the device will be blacklisted. In
> these cases the message \fIblacklisted, udev property missing\fR will
> be displayed.

ACK in general, but I'm preparing a larger update for the documentation
of the blacklist / whitelist handling, to be submitted very soon, which
might obsolete this.

Martin

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




More information about the dm-devel mailing list