From: ally heev <allyheev@gmail.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
Sumit Garg <sumit.garg@kernel.org>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH] tee: fix uninitialized pointers with free attr
Date: Mon, 10 Nov 2025 15:03:51 +0530 [thread overview]
Message-ID: <feffccdea0085f2a25f699bf80e5e8176ecd4128.camel@gmail.com> (raw)
In-Reply-To: <CAHUa44GYnZFaZQBNbV0=RSR7r61+ErYdQtEsRObNALz2CwT_Gg@mail.gmail.com>
On Mon, 2025-11-10 at 09:57 +0100, Jens Wiklander wrote:
[..]
> > diff --git a/drivers/tee/qcomtee/call.c b/drivers/tee/qcomtee/call.c
> > index ac134452cc9cfd384c28d41547545f2c5748d86c..8b7b4decddd8d1811dc0a7cc46a4a4fbada45526 100644
> > --- a/drivers/tee/qcomtee/call.c
> > +++ b/drivers/tee/qcomtee/call.c
> > @@ -645,12 +645,13 @@ static void qcomtee_get_version(struct tee_device *teedev,
> > static void qcomtee_get_qtee_feature_list(struct tee_context *ctx, u32 id,
> > u32 *version)
> > {
> > - struct qcomtee_object_invoke_ctx *oic __free(kfree);
> > struct qcomtee_object *client_env, *service;
> > struct qcomtee_arg u[3] = { 0 };
> > int result;
> >
> > - oic = qcomtee_object_invoke_ctx_alloc(ctx);
> > + struct qcomtee_object_invoke_ctx *oic __free(kfree) =
> > + qcomtee_object_invoke_ctx_alloc(ctx);
>
> Can we zero-initialize oic at its original location instead? Doing it
> here looks messy.
>
> Thanks,
> Jens
>
> > +
> > if (!oic)
> > return;
> >
> >
> > ---
> > base-commit: c9cfc122f03711a5124b4aafab3211cf4d35a2ac
> > change-id: 20251105-aheev-uninitialized-free-attr-tee-0221e45ec5a2
> >
> > Best regards,
> > --
> > Ally Heev <allyheev@gmail.com>
> >
Thanks, will fix it
Regards,
ALly
prev parent reply other threads:[~2025-11-10 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 14:20 [PATCH] tee: fix uninitialized pointers with free attr Ally Heev
2025-11-10 8:57 ` Jens Wiklander
2025-11-10 9:33 ` ally heev [this message]
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=feffccdea0085f2a25f699bf80e5e8176ecd4128.camel@gmail.com \
--to=allyheev@gmail.com \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=dan.carpenter@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox