From: Leon Romanovsky <leon@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>,
"Martin K. Petersen" <mkp@kernel.org>,
Yong Liu <pkfxxxing@gmail.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
security@kernel.org
Subject: Re: [PATCH v5 0/3] RDMA/srpt: Fix command initialization and read buffer disclosure
Date: Mon, 16 Nov 2026 07:32:38 -0500 [thread overview]
Message-ID: <179483235872.1361005.12065062548973022416.b4-ty@kernel.org> (raw)
In-Reply-To: <20261113083848.1517595-1-pkfxxxing@gmail.com>
On Fri, 13 Nov 2026 16:38:39 +0800, Yong Liu wrote:
> Thanks for the review and suggestions. This revision separates the BUSY
> initialization fix and the target core control-read buffer fix from the
> SRPT descriptor validation and read-tail clearing fix. Together they
> address the NULL pointer dereference on descriptor parsing errors and
> uninitialized target kernel memory disclosure to an initiator.
>
> Changes in v5:
> - Move BUSY command initialization into patch 1 and explain why the
> target_init_cmd() return value is ignored.
> - Clear all control-read SG entries in target core in patch 2.
> - In patch 3, log inconsistent descriptor lengths and zero the read tail
> with one sg_zero_buffer() call through the command's chained SG list.
> Remove the SRPT-specific DMA synchronization.
>
> [...]
Applied, thanks!
[1/3] RDMA/srpt: Initialize commands before returning BUSY
https://git.kernel.org/rdma/rdma/c/fcce7700cc48e7
[2/3] scsi: target: Clear all control read scatterlist entries
https://git.kernel.org/rdma/rdma/c/1ecb732b4524d3
[3/3] RDMA/srpt: Prevent uninitialized read buffer disclosure
https://git.kernel.org/rdma/rdma/c/317128ea4f21c9
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-11-16 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 3:08 [PATCH 0/1] RDMA/srpt: Fix read underflow information disclosure liuyong
2026-11-10 3:08 ` [PATCH 1/1] RDMA/srpt: Limit read data transfers to the command length liuyong
2026-11-10 5:28 ` [PATCH v2] " liuyong
2026-11-11 0:54 ` Bart Van Assche
2026-11-11 6:28 ` liuyong
2026-11-11 6:53 ` [PATCH v3] RDMA/srpt: Prevent uninitialized read buffer disclosure liuyong
2026-11-12 9:41 ` [PATCH v4] " liuyong
2026-11-12 21:33 ` Bart Van Assche
2026-11-13 8:38 ` [PATCH v5 0/3] RDMA/srpt: Fix command initialization and " Yong Liu
2026-11-13 8:38 ` [PATCH v5 1/3] RDMA/srpt: Initialize commands before returning BUSY Yong Liu
2026-11-13 8:38 ` [PATCH v5 2/3] scsi: target: Clear all control read scatterlist entries Yong Liu
2026-11-13 8:38 ` [PATCH v5 3/3] RDMA/srpt: Prevent uninitialized read buffer disclosure Yong Liu
2026-11-13 20:49 ` [PATCH v5 0/3] RDMA/srpt: Fix command initialization and " Bart Van Assche
2026-11-16 12:32 ` Leon Romanovsky [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=179483235872.1361005.12065062548973022416.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mkp@kernel.org \
--cc=pkfxxxing@gmail.com \
--cc=security@kernel.org \
--cc=target-devel@vger.kernel.org \
/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®