public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>
To: Bart Van Assche <bvanassche@acm.org>,
	Arthur Simchaev <Arthur.Simchaev@sandisk.com>,
	"quic_cang@quicinc.com" <quic_cang@quicinc.com>,
	"quic_nitirawa@quicinc.com" <quic_nitirawa@quicinc.com>,
	"avri.altman@wdc.com" <avri.altman@wdc.com>,
	"peter.wang@mediatek.com" <peter.wang@mediatek.com>,
	"manivannan.sadhasivam@linaro.org"
	<manivannan.sadhasivam@linaro.org>,
	"minwoo.im@samsung.com" <minwoo.im@samsung.com>,
	"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Bean Huo <beanhuo@micron.com>,
	Keoseong Park <keosung.park@samsung.com>,
	Ziqi Chen <quic_ziqichen@quicinc.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	"Gwendal Grignou" <gwendal@chromium.org>,
	Eric Biggers <ebiggers@google.com>,
	open list <linux-kernel@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support:Keyword:mediatek"
	<linux-arm-kernel@lists.infradead.org>,
	"moderated list:ARM/Mediatek SoC support:Keyword:mediatek"
	<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH v4 1/1] scsi: ufs: core: add device level exception support
Date: Thu, 27 Mar 2025 14:45:10 -0700	[thread overview]
Message-ID: <4cb20c80-9bb0-e147-e3c0-467f4c8828ba@quicinc.com> (raw)
In-Reply-To: <3d7b543c-1165-42e0-8471-25b04c7572ac@acm.org>

On 3/27/2025 4:36 AM, Bart Van Assche wrote:
> On 3/26/25 7:47 PM, Bao D. Nguyen wrote:
>> On 3/26/2025 3:49 AM, Bart Van Assche wrote:
>>> On 3/25/25 6:15 PM, Bao D. Nguyen wrote:
>>>> The existing "struct utp_upiu_query_v4_0" probably has a bug in it. 
>>>> It does not use the  __attribute__((__packed__)) attribute. The 
>>>> compiler is free to add padding in this structure, resulting in the 
>>>> read attribute value being incorrect. I plan to provide a separate 
>>>> patch to fix this issue.
>>>
>>> Adding __attribute__((__packed__)) or __packed to data structures that
>>> don't need it is not an improvement but is a change that makes
>>> processing slower on architectures that do not support unaligned
>>> accesses. Instead of adding __packed to data structures in their
>>> entirety, only add it to those members that need it and check the
>>> structure size as follows:
>>>
>>> static_assert(sizeof(...) == ...);
>>>
>> Thank you for the info on this, Bart.
>> IMO, this response upiu data should be __packed because the data 
>> coming from the hardware follows a strict format as defined by the 
>> spec. If we support __pack each individual field which data may be 
>> read by the driver (the attribute read commands) and check the 
>> validity of their sizes, it may add some complexity?
> 
> Hi Bao,
> 
> As explained in my previous email, adding __packed to data structures in
> their entirety is a bad practice. Please don't do this.
> 
> Regarding your question: I have not yet seen any data structure that
> represents an on-the-wire data format where every single data member
> has to be annotated with __packed. Only data members that are not
> aligned to a natural boundary need this annotation. Examples are
> available in this header file: include/scsi/srp.h.
> 

Thanks Bart. How about we change the current utp_upiu_query_v4_0 to

struct utp_upiu_query_v4_0 {
         __u8 opcode;
         __u8 idn;
         __u8 index;
         __u8 selector;
         __u8 cmd_specifics[8];
         /* private: */
         __be32 reserved;
};

Depending on the opcode/transaction, the cmd_specifics[] can be type 
casted to access the LENGTH, FLAG_VALUE, VALUE[0:63] fields of the QUERY 
UPIU. The __u8 array[8] would also prevent the compiler padding to the data.

Thanks, Bao



  reply	other threads:[~2025-03-27 21:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21  3:18 [PATCH v4 1/1] scsi: ufs: core: add device level exception support Bao D. Nguyen
2025-03-21 16:31 ` Bart Van Assche
2025-03-25 16:33 ` Arthur Simchaev
2025-03-25 22:15   ` Bao D. Nguyen
2025-03-26  7:30     ` Arthur Simchaev
2025-03-26 23:28       ` Bao D. Nguyen
2025-03-26 10:49     ` Bart Van Assche
2025-03-26 23:47       ` Bao D. Nguyen
2025-03-27 11:36         ` Bart Van Assche
2025-03-27 21:45           ` Bao D. Nguyen [this message]
2025-03-28 14:02             ` Bart Van Assche
2025-04-02  7:49               ` manivannan.sadhasivam
2025-04-02 19:00                 ` Bao D. Nguyen
2025-04-06 18:23                   ` manivannan.sadhasivam

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=4cb20c80-9bb0-e147-e3c0-467f4c8828ba@quicinc.com \
    --to=quic_nguyenb@quicinc.com \
    --cc=Arthur.Simchaev@sandisk.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=adrian.hunter@intel.com \
    --cc=alim.akhtar@samsung.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=bvanassche@acm.org \
    --cc=ebiggers@google.com \
    --cc=gwendal@chromium.org \
    --cc=keosung.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=matthias.bgg@gmail.com \
    --cc=minwoo.im@samsung.com \
    --cc=peter.wang@mediatek.com \
    --cc=quic_cang@quicinc.com \
    --cc=quic_nitirawa@quicinc.com \
    --cc=quic_ziqichen@quicinc.com \
    --cc=viro@zeniv.linux.org.uk \
    /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