From: Sumit Garg <sumit.garg@linaro.org>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
OP-TEE TrustedFirmware <op-tee@lists.trustedfirmware.org>,
Devicetree List <devicetree@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jerome Forissier <jerome@forissier.org>,
Etienne Carriere <etienne.carriere@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Ard Biesheuvel <ardb@kernel.org>, Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH v6 3/6] tee: fix put order in teedev_close_context()
Date: Wed, 13 Oct 2021 12:39:02 +0530 [thread overview]
Message-ID: <CAFA6WYPZ-JbAhfvdWfbcgqBRnA9F-=o5k=ZzR_KYL+rAkVm3PA@mail.gmail.com> (raw)
In-Reply-To: <20211006071546.2540920-4-jens.wiklander@linaro.org>
On Wed, 6 Oct 2021 at 12:45, Jens Wiklander <jens.wiklander@linaro.org> wrote:
>
> Prior to this patch was teedev_close_context() calling tee_device_put()
> before teedev_ctx_put() leading to teedev_ctx_release() accessing
> ctx->teedev just after the reference counter was decreased on the
> teedev. Fix this by calling teedev_ctx_put() before tee_device_put().
>
> Fixes: 217e0250cccb ("tee: use reference counting for tee_context")
> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
> ---
> drivers/tee/tee_core.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
-Sumit
> diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c
> index 2b37bc408fc3..85102d12d716 100644
> --- a/drivers/tee/tee_core.c
> +++ b/drivers/tee/tee_core.c
> @@ -98,8 +98,10 @@ void teedev_ctx_put(struct tee_context *ctx)
>
> static void teedev_close_context(struct tee_context *ctx)
> {
> - tee_device_put(ctx->teedev);
> + struct tee_device *teedev = ctx->teedev;
> +
> teedev_ctx_put(ctx);
> + tee_device_put(teedev);
> }
>
> static int tee_open(struct inode *inode, struct file *filp)
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-10-13 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 7:15 [PATCH v6 0/6] Asynchronous notifications from secure world Jens Wiklander
2021-10-06 7:15 ` [PATCH v6 1/6] docs: staging/tee.rst: add a section on OP-TEE notifications Jens Wiklander
2021-10-13 7:02 ` Sumit Garg
2021-10-06 7:15 ` [PATCH v6 2/6] dt-bindings: arm: optee: add interrupt property Jens Wiklander
2021-10-13 7:08 ` Sumit Garg
2021-10-06 7:15 ` [PATCH v6 3/6] tee: fix put order in teedev_close_context() Jens Wiklander
2021-10-13 7:09 ` Sumit Garg [this message]
2021-10-06 7:15 ` [PATCH v6 4/6] tee: export teedev_open() and teedev_close_context() Jens Wiklander
2021-10-13 7:09 ` Sumit Garg
2021-10-06 7:15 ` [PATCH v6 5/6] optee: separate notification functions Jens Wiklander
2021-10-13 7:15 ` Sumit Garg
2021-10-13 13:42 ` Jens Wiklander
2021-10-06 7:15 ` [PATCH v6 6/6] optee: add asynchronous notifications Jens Wiklander
2021-10-13 8:07 ` Sumit Garg
2021-10-14 5:42 ` 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='CAFA6WYPZ-JbAhfvdWfbcgqBRnA9F-=o5k=ZzR_KYL+rAkVm3PA@mail.gmail.com' \
--to=sumit.garg@linaro.org \
--cc=ardb@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=etienne.carriere@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=jerome@forissier.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=robh+dt@kernel.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).