From: sashiko-bot@kernel.org
To: "John Garry" <john.g.garry@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v5 20/27] scsi-multipath: add scsi_mpath_{start,end}_request()
Date: Mon, 27 Jul 2026 15:25:57 +0000 [thread overview]
Message-ID: <20260727152558.3565D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260727144234.3802948-21-john.g.garry@oracle.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Critical] Synchronous dispatch errors and request cancellations bypass `scsi_mpath_end_request()`, permanently leaking resources and causing NULL pointer dereferences on recycled tags.
- [Critical] The dummy implementation of `scsi_mpath_end_request()` skips `blk_update_request()`, silently dropping bio completions if CONFIG_SCSI_MULTIPATH is disabled.
--
--- Patch [20]: [PATCH v5 20/27] scsi-multipath: add scsi_mpath_{start,end}_request() ---
commit 375ed243ce77c97b0b6e6eb569248a68ab42aec6
Author: John Garry <john.garry@linux.dev>
scsi-multipath: add scsi_mpath_{start,end}_request()
This commit introduces scsi_mpath_start_request() and scsi_mpath_end_request()
to update private multipath request data. It also adds mpath_nr_active to
Scsi_Host to support queue depth multipath iopolicies.
> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> index 6a2d7dbfbe8c3..36e5c5543754f 100644
> --- a/drivers/scsi/scsi_lib.c
> +++ b/drivers/scsi/scsi_lib.c
> @@ -669,7 +669,10 @@ static bool scsi_end_request(struct request *req, blk_status_t error,
> struct scsi_device *sdev = cmd->device;
> struct request_queue *q = sdev->request_queue;
>
> - if (blk_update_request(req, error, bytes))
> + if (is_mpath_request(req)) {
> + if (scsi_mpath_end_request(req, error, bytes))
> + return true;
> + } else if (blk_update_request(req, error, bytes))
> return true;
[Severity: Critical]
If CONFIG_SCSI_MULTIPATH is disabled, the dummy stub for
scsi_mpath_end_request() unconditionally returns false.
If a request has REQ_MPATH set (which aliases REQ_DRV and can be set by
other subsystems like Device Mapper), won't the else if branch be completely
skipped?
Could this result in blk_update_request() never being called, leaking bios
and hanging the submitting task waiting for completion?
> [ ... ]
> diff --git a/drivers/scsi/scsi_multipath.c b/drivers/scsi/scsi_multipath.c
> index d79e1b7b90051..eae5864ce5826 100644
> --- a/drivers/scsi/scsi_multipath.c
> +++ b/drivers/scsi/scsi_multipath.c
> [ ... ]
> +bool scsi_mpath_end_request(struct request *req, blk_status_t error,
> + unsigned int nr_bytes)
> +{
> + struct scsi_cmnd *scmd = blk_mq_rq_to_pdu(req);
> + struct scsi_device *sdev = scmd->device;
> + struct block_device *bi_bdev = NULL;
> +
> + if (scmd->flags & SCMD_MPATH_IO_STATS) {
> + struct bio *clone = req->bio, *master = clone->bi_private;
> +
> + bi_bdev = master->bi_bdev;
> + }
[Severity: Critical]
If a request is requeued, SCMD_MPATH_IO_STATS and SCMD_MPATH_CNT_ACTIVE are
preserved by SCMD_PRESERVED_FLAGS. If the request later fails an early state
check in scsi_queue_rq() (e.g., the device goes offline), blk-mq ends it
directly via blk_mq_end_request(), bypassing scsi_end_request().
When the tag is reused for a dataless request, scsi_mpath_start_request()
returns early without clearing the flags. Will this cause
scsi_mpath_end_request() to read the leaked SCMD_MPATH_IO_STATS flag and
dereference req->bio which is NULL?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260727144234.3802948-1-john.g.garry@oracle.com?part=20
next prev parent reply other threads:[~2026-07-27 15:25 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 14:42 [PATCH v5 00/27] Native SCSI Multipath support John Garry
2026-07-27 14:42 ` [PATCH v5 01/27] libmultipath: Add initial framework John Garry
2026-07-27 15:05 ` sashiko-bot
2026-07-27 15:12 ` John Garry
2026-07-27 14:42 ` [PATCH v5 02/27] libmultipath: Add basic gendisk support John Garry
2026-07-27 15:04 ` sashiko-bot
2026-07-27 15:15 ` John Garry
2026-07-27 14:42 ` [PATCH v5 03/27] libmultipath: Add path selection support John Garry
2026-07-27 15:03 ` sashiko-bot
2026-07-27 15:20 ` John Garry
2026-07-27 14:42 ` [PATCH v5 04/27] libmultipath: Add bio handling John Garry
2026-07-27 14:42 ` [PATCH v5 05/27] libmultipath: Add support for mpath_device management John Garry
2026-07-27 15:03 ` sashiko-bot
2026-07-27 15:23 ` John Garry
2026-07-27 14:42 ` [PATCH v5 06/27] libmultipath: Add delayed removal support John Garry
2026-07-27 15:00 ` sashiko-bot
2026-07-27 15:25 ` John Garry
2026-07-27 14:42 ` [PATCH v5 07/27] libmultipath: Add sysfs helpers John Garry
2026-07-27 15:03 ` sashiko-bot
2026-07-27 15:33 ` John Garry
2026-07-27 14:42 ` [PATCH v5 08/27] libmultipath: Add support for block device IOCTL John Garry
2026-07-27 15:08 ` sashiko-bot
2026-07-27 15:31 ` John Garry
2026-07-27 14:42 ` [PATCH v5 09/27] libmultipath: Add mpath_bdev_getgeo() John Garry
2026-07-27 14:42 ` [PATCH v5 10/27] libmultipath: Add mpath_bdev_get_unique_id() John Garry
2026-07-27 14:42 ` [PATCH v5 11/27] scsi-multipath: introduce basic SCSI device support John Garry
2026-07-27 18:59 ` sashiko-bot
2026-07-27 14:42 ` [PATCH v5 12/27] scsi-multipath: introduce scsi_device head structure John Garry
2026-07-27 15:15 ` sashiko-bot
2026-07-27 15:37 ` John Garry
2026-07-27 14:42 ` [PATCH v5 13/27] scsi-multipath: provide sysfs link from to scsi_device John Garry
2026-07-27 15:07 ` sashiko-bot
2026-07-27 16:21 ` John Garry
2026-07-27 14:42 ` [PATCH v5 14/27] scsi-multipath: support iopolicy John Garry
2026-07-27 15:06 ` sashiko-bot
2026-07-27 15:39 ` John Garry
2026-07-27 14:42 ` [PATCH v5 15/27] scsi-multipath: clone each bio John Garry
2026-07-27 15:21 ` sashiko-bot
2026-07-27 15:40 ` John Garry
2026-07-27 14:42 ` [PATCH v5 16/27] scsi-multipath: clear path when device is blocked John Garry
2026-07-27 15:14 ` sashiko-bot
2026-07-27 15:44 ` John Garry
2026-07-27 14:42 ` [PATCH v5 17/27] scsi-multipath: revalidate paths upon device unblock John Garry
2026-07-27 15:17 ` sashiko-bot
2026-07-27 16:05 ` John Garry
2026-07-27 14:42 ` [PATCH v5 18/27] scsi-multipath: failover handling John Garry
2026-07-27 14:42 ` [PATCH v5 19/27] scsi-multipath: provide callbacks for path state John Garry
2026-07-27 15:24 ` sashiko-bot
2026-07-27 16:07 ` John Garry
2026-07-27 14:42 ` [PATCH v5 20/27] scsi-multipath: add scsi_mpath_{start,end}_request() John Garry
2026-07-27 15:25 ` sashiko-bot [this message]
2026-07-27 16:18 ` John Garry
2026-07-27 14:42 ` [PATCH v5 21/27] scsi-multipath: add delayed disk removal support John Garry
2026-07-27 15:23 ` sashiko-bot
2026-07-27 16:20 ` John Garry
2026-07-27 14:42 ` [PATCH v5 22/27] scsi: sd: add multipath disk class John Garry
2026-07-27 15:14 ` sashiko-bot
2026-07-27 16:21 ` John Garry
2026-07-27 14:42 ` [PATCH v5 23/27] scsi: sd: add multipath disk attr groups John Garry
2026-07-27 15:20 ` sashiko-bot
2026-07-27 16:22 ` John Garry
2026-07-27 14:42 ` [PATCH v5 24/27] scsi: sd: support multipath disk John Garry
2026-07-27 15:20 ` sashiko-bot
2026-07-27 16:33 ` John Garry
2026-07-27 14:42 ` [PATCH v5 25/27] scsi: sd: add mpath_dev file John Garry
2026-07-27 15:33 ` sashiko-bot
2026-07-27 16:24 ` John Garry
2026-07-27 14:42 ` [PATCH v5 26/27] scsi: sd: add mpath_numa_nodes dev attribute John Garry
2026-07-27 14:42 ` [PATCH v5 27/27] scsi: sd: add mpath_queue_depth " John Garry
2026-07-27 15:28 ` sashiko-bot
2026-07-27 15:29 ` John Garry
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=20260727152558.3565D1F000E9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox