From: Stanley Jhu <stanleyjhu@google.com>
To: Daejun Park <daejun7.park@samsung.com>, qemu-devel@nongnu.org
Cc: Jeuk Kim <jeuk20.kim@samsung.com>,
farosas@suse.de, lvivier@redhat.com, pbonzini@redhat.com,
kwolf@redhat.com, hreitz@redhat.com, qemu-block@nongnu.org,
pierrick.bouvier@oss.qualcomm.com
Subject: Re: [PATCH v2 3/6] hw/ufs: Limit data transfers to the transfer length of the CDB
Date: Mon, 19 Oct 2026 16:03:21 +0800 [thread overview]
Message-ID: <20261019080321.1982926-1-stanleyjhu@google.com> (raw)
In-Reply-To: <20261019013307epcms2p14049cf5797cbe5332877ddeb950f18bc@epcms2p1>
On Mon, 19 Oct 2026 10:33:07 +0900, Daejun Park wrote:
> UFSHCI reports a data buffer that is too small with OCS MISMATCH DATA
> BUFFER SIZE, so the status belongs to ufs.c. ufs.c does not parse the
> CDB, though; the LU does, in scsi_req_new(). In v3 the LU would pass
> the transfer length to ufs.c, and ufs.c would fail the request with
> that OCS when the PRDT is smaller, before scsi-hd sees it and with the
> write pointer unchanged. Would that split work for you?
Yes, that split sounds good to me. Thanks.
Stanley
next prev parent reply other threads:[~2026-10-19 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20261016092423epcms2p83f80a8dd8f7c1ddc3a94541e0771c306@epcms2p8>
2026-10-16 9:24 ` [PATCH v2 0/6] Support for Zoned UFS Daejun Park
2026-10-16 9:25 ` [PATCH v2 1/6] hw/ufs: Fail SCSI commands that move data without a PRDT Daejun Park
2026-10-16 9:27 ` [PATCH v2 2/6] hw/ufs: Pass SYNCHRONIZE CACHE(16) to scsi-hd as SYNCHRONIZE CACHE(10) Daejun Park
2026-10-16 9:31 ` [PATCH v2 3/6] hw/ufs: Limit data transfers to the transfer length of the CDB Daejun Park
2026-10-16 11:54 ` Stanley Jhu
2026-10-19 1:33 ` Daejun Park
2026-10-19 8:03 ` Stanley Jhu [this message]
2026-10-16 9:32 ` [PATCH v2 4/6] docs/system: Document zoned UFS logical units Daejun Park
2026-10-16 9:33 ` [PATCH v2 5/6] hw/ufs: Support for Zoned UFS Daejun Park
2026-10-16 11:54 ` Stanley Jhu
2026-10-19 1:32 ` Daejun Park
2026-10-16 9:35 ` [PATCH v2 6/6] tests/qtest: Add tests " Daejun Park
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=20261019080321.1982926-1-stanleyjhu@google.com \
--to=stanleyjhu@google.com \
--cc=daejun7.park@samsung.com \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=jeuk20.kim@samsung.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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 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.