From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Xose Vazquez Perez <xose.vazquez@gmail.com>,
dm-devel@lists.linux.dev
Subject: Re: [PATCH 2/2] libmultipath/foreign/nvme: fix return value check in get_ctrl_blkdev()
Date: Mon, 8 Sep 2025 14:54:45 -0400 [thread overview]
Message-ID: <aL8mdcK6jyd1xHb6@redhat.com> (raw)
In-Reply-To: <20250905210714.167202-3-mwilck@suse.com>
On Fri, Sep 05, 2025 at 11:07:14PM +0200, Martin Wilck wrote:
> Only a negative return value from udev_enumerate_add_match_subsystem()
> indicates an error.
>
> Fixes: 7b47762 ("libmultipath: nvme: fix path detection for kernel 4.16")
>
> Signed-off-by: Martin Wilck <mwilck@suse.com>
Reviewed-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
> libmultipath/foreign/nvme.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libmultipath/foreign/nvme.c b/libmultipath/foreign/nvme.c
> index 0d19303..4cbdf60 100644
> --- a/libmultipath/foreign/nvme.c
> +++ b/libmultipath/foreign/nvme.c
> @@ -536,7 +536,7 @@ struct udev_device *get_ctrl_blkdev(const struct context *ctx,
> pthread_cleanup_push(_udev_enumerate_unref, enm);
> if (udev_enumerate_add_match_parent(enm, ctrl) < 0)
> goto out;
> - if (udev_enumerate_add_match_subsystem(enm, "block"))
> + if (udev_enumerate_add_match_subsystem(enm, "block") < 0)
> goto out;
>
> if (udev_enumerate_scan_devices(enm) < 0) {
> --
> 2.51.0
prev parent reply other threads:[~2025-09-08 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 21:07 [PATCH 0/2] multipath-tools 0.12.0 - late minor fixes Martin Wilck
2025-09-05 21:07 ` [PATCH 1/2] libmultipath: fix missing return value check in snprint_devices() Martin Wilck
2025-09-08 18:34 ` Benjamin Marzinski
2025-09-09 8:57 ` Martin Wilck
2025-09-05 21:07 ` [PATCH 2/2] libmultipath/foreign/nvme: fix return value check in get_ctrl_blkdev() Martin Wilck
2025-09-08 18:54 ` Benjamin Marzinski [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=aL8mdcK6jyd1xHb6@redhat.com \
--to=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=martin.wilck@suse.com \
--cc=xose.vazquez@gmail.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.