mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yingjie Wang <x-professor@outlook.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>,
	"mkp@kernel.org" <mkp@kernel.org>,
	"yangxiuwei@kylinos.cn" <yangxiuwei@kylinos.cn>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 2/6] scsi: sr: release CDDA request before copying to userspace
Date: Thu, 22 Oct 2026 07:51:53 +0000	[thread overview]
Message-ID: <20261022.scsi-cdda-lifetime.8f31a2c97b42@outlook.com> (raw)
In-Reply-To: <035f0183-a748-4eaa-a6a6-a358944535fa@acm.org>

Hi Bart,

> This change triggers a use-after-free because blk_mq_free_request()
> calls bio_put(), isn't it?

I checked this on the series base, 0fcb05b72344. In this path,
blk_mq_free_request() releases the completed request. It does not put
the BIO chain saved from rq->bio; blk_rq_unmap_user() later walks that
chain and releases it.

sr_read_cdda_bpc() saves rq->bio before blk_execute_rq(). After
completion, the patch reads scmd->result and, when needed, normalizes
the sense data before freeing the request. After
blk_mq_free_request(), it only calls blk_rq_unmap_user(bio); neither rq
nor scmd is accessed again.

The same ownership split is used by sg_rq_end_io(), which frees the
request while retaining srp->bio for later unmapping. The deferred
completion branch of nvme_uring_cmd_end_io() also returns
RQ_END_IO_FREE while leaving pdu->bio to be unmapped in task work.

Based on this ownership, I do not see a use-after-free introduced by
patch 2/6. Please let me know if you had a different ownership path in
mind.

Thanks,
Yingjie

  reply	other threads:[~2026-10-22  7:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 15:41 [PATCH 0/6] scsi: make SG_IO user copyback failure-safe Wang Yingjie
2026-10-18 15:41 ` [PATCH 1/6] scsi: core: release SG_IO request before copying to userspace Wang Yingjie
2026-10-18 15:41 ` [PATCH 2/6] scsi: sr: release CDDA " Wang Yingjie
2026-10-19 20:33   ` Bart Van Assche
2026-10-22  7:51     ` Yingjie Wang [this message]
2026-10-18 15:41 ` [PATCH 3/6] scsi: bsg: release synchronous request before user copyback Wang Yingjie
2026-10-18 15:41 ` [PATCH 4/6] scsi: bsg: report synchronous data copyback failures Wang Yingjie
2026-10-18 15:41 ` [PATCH 5/6] scsi: bsg: release io_uring request before user copyback Wang Yingjie
2026-10-18 15:41 ` [PATCH 6/6] scsi: bsg: report io_uring data copyback failures Wang Yingjie
2026-10-18 16:41 ` [PATCH 0/6] scsi: make SG_IO user copyback failure-safe Bart Van Assche
2026-10-19  6:32   ` Wang Yingjie
2026-10-19 21:11     ` Bart Van Assche
2026-10-22  7:52       ` Yingjie Wang

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=20261022.scsi-cdda-lifetime.8f31a2c97b42@outlook.com \
    --to=x-professor@outlook.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mkp@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yangxiuwei@kylinos.cn \
    /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

all inboxes | Powered by JetHome®