From: Sumit Garg via OP-TEE <op-tee@lists.trustedfirmware.org>
To: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
Cc: Arnd Bergmann <arnd@kernel.org>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Sumit Garg <sumit.garg@oss.qualcomm.com>,
Arnd Bergmann <arnd@arndb.de>, Alexandre Ghiti <alex@ghiti.fr>,
Etienne Carriere <etienne.carriere@foss.st.com>,
Randy Dunlap <rdunlap@infradead.org>,
op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH] tee: fix tee_ioctl_object_invoke_arg padding
Date: Mon, 8 Dec 2025 17:50:59 +0530 [thread overview]
Message-ID: <aTbCqyOuprPOyU4X@sumit-X1> (raw)
In-Reply-To: <0b061075-ab71-4ac1-93ec-438ddaaec903@oss.qualcomm.com>
On Mon, Dec 08, 2025 at 04:24:17PM +1100, Amirreza Zarrabi wrote:
> Hi,
>
> On 12/5/2025 12:27 AM, Jens Wiklander wrote:
> > Hi,
> >
> > On Thu, Dec 4, 2025 at 11:17 AM Arnd Bergmann <arnd@kernel.org> wrote:
> >>
> >> From: Arnd Bergmann <arnd@arndb.de>
> >>
> >> The tee_ioctl_object_invoke_arg structure has padding on some
> >> architectures but not on x86-32 and a few others:
> >>
> >> include/linux/tee.h:474:32: error: padding struct to align 'params' [-Werror=padded]
> >>
> >> I expect that all current users of this are on architectures that do
> >> have implicit padding here (arm64, arm, x86, riscv), so make the padding
> >> explicit in order to avoid surprises if this later gets used elsewhere.
> >>
> >> Fixes: d5b8b0fa1775 ("tee: add TEE_IOCTL_PARAM_ATTR_TYPE_OBJREF")
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >> ---
> >> The new interface showed up in 6.18, but I only came across this after
> >> that was released. Changing it now is technically an ABI change on
> >> architectures with unusual padding rules, so please consider carefully
> >> whether we want to do it this way or not.
> >>
> >> Working around the ABI differences without an ABI change is possible,
> >> but adds a lot of complexity for compat handling.
> >
> > This is currently only used by the recently introduced qcomtee backend
> > driver. So it's only used on a few arm64 Qualcomm platforms right now.
> >
> > I think we should take this patch, but let's hear what others think.
Yeah since it's not an ABI issue on arm64 platforms where QTEE runs, so:
Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
> >
> > Thanks,
> > Jens
> >
>
> I agree. We should take this patch. As noted, there are not many
> clients relying on it yet, so updating the userspace should
> be straightforward.
You should rather test without any userspace library update to test it's
not an ABI issue. Just for correctness sake, you can update the library
too.
-Sumit
[...]
next prev parent reply other threads:[~2025-12-08 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 10:17 [PATCH] tee: fix tee_ioctl_object_invoke_arg padding Arnd Bergmann via OP-TEE
2025-12-04 13:27 ` Jens Wiklander
2025-12-05 13:45 ` Harshal Dev via OP-TEE
2025-12-05 13:56 ` Arnd Bergmann
2025-12-05 14:11 ` Harshal Dev via OP-TEE
2025-12-08 5:24 ` Amirreza Zarrabi via OP-TEE
2025-12-08 12:20 ` Sumit Garg via OP-TEE [this message]
2025-12-08 12:54 ` Harshal Dev via OP-TEE
2025-12-09 3:54 ` Amirreza Zarrabi via OP-TEE
2025-12-16 7:48 ` Jens Wiklander
2025-12-16 10:55 ` Harshal Dev via OP-TEE
2025-12-16 13:17 ` Jens Wiklander
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=aTbCqyOuprPOyU4X@sumit-X1 \
--to=op-tee@lists.trustedfirmware.org \
--cc=alex@ghiti.fr \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=etienne.carriere@foss.st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rdunlap@infradead.org \
--cc=sumit.garg@kernel.org \
--cc=sumit.garg@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