From: Laurence Oberman <loberman@redhat.com>
To: Christoph Hellwig <hch@lst.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
Ming Lei <ming.lei@redhat.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, "Ewan D. Milne" <emilne@redhat.com>,
linux-rdma@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: fix virt_boundary_mask handling in SCSI
Date: Tue, 24 Jun 2025 10:21:36 -0400 [thread overview]
Message-ID: <a665dead67bf4f3432cf1bddf29d2c573ab71673.camel@redhat.com> (raw)
In-Reply-To: <20250623080326.48714-1-hch@lst.de>
On Mon, 2025-06-23 at 10:02 +0200, Christoph Hellwig wrote:
> Hi all,
>
> this series fixes a corruption when drivers using virt_boundary_mask
> set
> a limited max_segment_size by accident, which Red Hat reported as
> causing
> data corruption with storvsc. I did audit the tree and also found
> that
> this can affect SRP and iSER as well.
>
> Note that I've dropped the Tested-by from Laurence because the patch
> changed very slightly from the last version.
>
> Diffstat:
> infiniband/ulp/srp/ib_srp.c | 5 +++--
> scsi/hosts.c | 20 +++++++++++++-------
> 2 files changed, 16 insertions(+), 9 deletions(-)
>
Grabbing latest and will test tomorrow and reply
next prev parent reply other threads:[~2025-06-24 14:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 8:02 fix virt_boundary_mask handling in SCSI Christoph Hellwig
2025-06-23 8:02 ` [PATCH 1/2] RDMA/srp: don't set a max_segment_size when virt_boundary_mask is set Christoph Hellwig
2025-06-23 15:31 ` Bart Van Assche
2025-06-24 5:57 ` Hannes Reinecke
2025-06-23 8:02 ` [PATCH 2/2] scsi: enforce unlimited " Christoph Hellwig
2025-06-23 8:37 ` John Garry
2025-06-23 13:35 ` Christoph Hellwig
2025-06-23 14:03 ` John Garry
2025-06-23 14:05 ` Christoph Hellwig
2025-06-23 9:50 ` Ming Lei
2025-06-24 5:57 ` Hannes Reinecke
2025-06-24 14:21 ` Laurence Oberman [this message]
2025-06-24 16:11 ` fix virt_boundary_mask handling in SCSI Laurence Oberman
2025-06-24 16:13 ` Laurence Oberman
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=a665dead67bf4f3432cf1bddf29d2c573ab71673.camel@redhat.com \
--to=loberman@redhat.com \
--cc=bvanassche@acm.org \
--cc=emilne@redhat.com \
--cc=haiyangz@microsoft.com \
--cc=hch@lst.de \
--cc=kys@microsoft.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=wei.liu@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;
as well as URLs for NNTP newsgroup(s).