From: sashiko-bot@kernel.org
To: "John Garry" <john.g.garry@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v3 09/10] nvme-multipath: add nvme_mpath_head_queue_if_no_path()
Date: Fri, 03 Jul 2026 11:33:39 +0000 [thread overview]
Message-ID: <20260703113340.014FA1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260703103204.3724406-10-john.g.garry@oracle.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added wrapper nvme_mpath_head_queue_if_no_path() calls an undefined function mpath_head_queue_if_no_path(). The required header <linux/multipath.h> and the underlying libmultipath implementation are missing from the kernel tree and this patch series. Compiling the kernel with CONFIG_NVME_MULTIPATH=y will result in a build failure.
--
commit cff4d8c98386c9683c8dc00a277d4f52cdd8c6a0
Author: John Garry <john.g.garry@oracle.com>
nvme-multipath: add nvme_mpath_head_queue_if_no_path()
This commit adds a wrapper function to check if the multipath head should
queue when there are no paths. It provides both an active implementation
and a stub for when CONFIG_NVME_MULTIPATH is disabled.
> diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
> index 9fd958a426f1f..354f77dea4870 100644
> --- a/drivers/nvme/host/nvme.h
> +++ b/drivers/nvme/host/nvme.h
> @@ -1095,6 +1095,11 @@ static inline void nvme_mpath_synchronize(struct nvme_ns_head *head)
> mpath_synchronize(&head->mpath_head);
> }
>
> +static inline bool nvme_mpath_head_queue_if_no_path(struct nvme_ns_head *head)
> +{
> + return mpath_head_queue_if_no_path(&head->mpath_head);
[Severity: Low]
Does this cause a build failure when CONFIG_NVME_MULTIPATH=y?
It appears that mpath_head_queue_if_no_path() is currently undefined. I
couldn't find a declaration or the underlying implementation for it in the
kernel tree. Compiling with this configuration might result in an undefined
reference or missing header error.
> +}
> +
> static inline void nvme_trace_bio_complete(struct request *req)
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260703103204.3724406-1-john.g.garry@oracle.com?part=9
next prev parent reply other threads:[~2026-07-03 11:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 10:31 [PATCH v3 00/10] nvme: switch to libmultipath John Garry
2026-07-03 10:31 ` [PATCH v3 01/10] nvme-multipath: add initial support for using libmultipath John Garry
2026-07-03 10:44 ` sashiko-bot
2026-07-03 10:31 ` [PATCH v3 02/10] nvme-multipath: add nvme_mpath_available_path() John Garry
2026-07-03 10:31 ` [PATCH v3 03/10] nvme-multipath: add nvme_mpath_{add, remove}_cdev() John Garry
2026-07-03 10:31 ` [PATCH v3 04/10] nvme-multipath: add nvme_mpath_is_{disabled, optimised} John Garry
2026-07-03 11:06 ` sashiko-bot
2026-07-03 10:31 ` [PATCH v3 05/10] nvme-multipath: add nvme_mpath_cdev_ioctl() John Garry
2026-07-03 11:11 ` sashiko-bot
2026-07-03 10:32 ` [PATCH v3 06/10] nvme-multipath: add uring_cmd support John Garry
2026-07-03 11:42 ` sashiko-bot
2026-07-03 10:32 ` [PATCH v3 07/10] nvme-multipath: add nvme_mpath_synchronize() John Garry
2026-07-03 11:24 ` sashiko-bot
2026-07-03 14:50 ` John Garry
2026-07-03 10:32 ` [PATCH v3 08/10] nvme-multipath: add nvme_{add,delete}_ns() John Garry
2026-07-03 11:24 ` sashiko-bot
2026-07-03 10:32 ` [PATCH v3 09/10] nvme-multipath: add nvme_mpath_head_queue_if_no_path() John Garry
2026-07-03 11:33 ` sashiko-bot [this message]
2026-07-03 10:32 ` [PATCH v3 10/10] nvme-multipath: switch to use libmultipath John Garry
2026-07-03 11:42 ` sashiko-bot
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=20260703113340.014FA1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.