Re: [PATCH 3/3] multipathd: don't update paths in INIT_MISSING_UDEV

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2025-03-24 at 16:55 -0400, Benjamin Marzinski wrote:
> There is nothing for update_uninitialized_path() to do for paths in
> the
> INIT_MISSING_UDEV state. In fact, there shouldn't be any paths in
> this
> state when update_uninitialized_path() is called, since they will
> have
> switched to a different state in check_uninitialized_path().
> 
> Signed-off-by: Benjamin Marzinski <bmarzins@xxxxxxxxxx>

Reviewed-by: Martin Wilck  <mwilck@xxxxxxxx>


> ---
>  multipathd/main.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/multipathd/main.c b/multipathd/main.c
> index ecad5a4f..9c44e6e6 100644
> --- a/multipathd/main.c
> +++ b/multipathd/main.c
> @@ -2889,7 +2889,6 @@ update_uninitialized_path(struct vectors *
> vecs, struct path * pp)
>  	struct config *conf;
>  
>  	if (pp->initialized != INIT_NEW && pp->initialized !=
> INIT_FAILED &&
> -	    pp->initialized != INIT_MISSING_UDEV &&
>  	    pp->initialized != INIT_OFFLINE)
>  		return CHECK_PATH_SKIPPED;
>  






[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux