From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Keoseong Park <keosung.park@samsung.com>
Cc: ALIM AKHTAR <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"peter.wang@mediatek.com" <peter.wang@mediatek.com>,
"tanghuan@vivo.com" <tanghuan@vivo.com>,
"zhongqiu.han@oss.qualcomm.com" <zhongqiu.han@oss.qualcomm.com>,
"quic_nguyenb@quicinc.com" <quic_nguyenb@quicinc.com>,
"liu.song13@zte.com.cn" <liu.song13@zte.com.cn>,
"chullee@google.com" <chullee@google.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi: ufs: core: Handle sentinel value for dHIDAvailableSize
Date: Fri, 16 Jan 2026 23:11:36 -0500 [thread overview]
Message-ID: <yq1pl78j2to.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20251226042825epcms2p6f02ba12fa97ff4a69c00f6fb9ff55603@epcms2p6> (Keoseong Park's message of "Fri, 26 Dec 2025 13:28:25 +0900")
Keoseong,
> JEDEC UFS spec defines 0xFFFFFFFF for dHIDAvailableSize as indicating no
> valid fragmented size information. Returning the raw value can mislead
> userspace. Return -ENODATA instead when the value is unavailable.
Applied to 6.20/scsi-staging, thanks!
--
Martin K. Petersen
next prev parent reply other threads:[~2026-01-17 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251226042825epcms2p6f02ba12fa97ff4a69c00f6fb9ff55603@epcms2p6>
2025-12-26 4:28 ` [PATCH] scsi: ufs: core: Handle sentinel value for dHIDAvailableSize Keoseong Park
2026-01-13 7:24 ` Peter Wang (王信友)
2026-01-13 16:42 ` Bart Van Assche
2026-01-17 4:11 ` Martin K. Petersen [this message]
2026-01-24 3:50 ` Martin K. Petersen
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=yq1pl78j2to.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=chullee@google.com \
--cc=keosung.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liu.song13@zte.com.cn \
--cc=peter.wang@mediatek.com \
--cc=quic_nguyenb@quicinc.com \
--cc=tanghuan@vivo.com \
--cc=zhongqiu.han@oss.qualcomm.com \
/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