public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bao D. Nguyen" <quic_nguyenb@quicinc.com>
To: "manivannan.sadhasivam@linaro.org"
	<manivannan.sadhasivam@linaro.org>,
	Bart Van Assche <bvanassche@acm.org>
Cc: 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>,
	"minwoo.im@samsung.com" <minwoo.im@samsung.com>,
	"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"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: Wed, 2 Apr 2025 12:00:26 -0700	[thread overview]
Message-ID: <1b87152e-ff0f-9c45-020d-4927ff3dbef8@quicinc.com> (raw)
In-Reply-To: <yzy7oad77h744vf2bdylkm4fronemjwvrmlstnj6x5lzjxg672@zya6toqv4aeg>

On 4/2/2025 12:49 AM, manivannan.sadhasivam@linaro.org wrote:
> Yeah, we should be cautious in changing the uAPI header as it can break the
> userspace applications. Annotating the members that need packed attribute seems
> like the way forward to me.

Yes, I realized potential issue when Bart raised a concern.

> 
> Though, I'd like to understand which architecture has the alignment constraint
> in this structure. Only if an architecture requires 8 byte alignment for __be32
> would be a problem. That too only for osf7 and reserved. But I'm not aware of
> such architectures in use.
When using "__u64 value;" in place of osf3-6, I saw the compiler padded 
4 bytes, so __packed was needed for me to get correct __u64 value. I 
thought even the existing structure utp_upiu_query_v4_0 may need 
__packed on some fields where the driver reads the returned data in 
order to be safe across all architectures. However, without evidence of 
an actual failure, I didn't touch the existing structure. Only raised 
potential issue for discussion.

Thanks, Bao

  reply	other threads:[~2025-04-02 19:01 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
2025-03-28 14:02             ` Bart Van Assche
2025-04-02  7:49               ` manivannan.sadhasivam
2025-04-02 19:00                 ` Bao D. Nguyen [this message]
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=1b87152e-ff0f-9c45-020d-4927ff3dbef8@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