archive mirror
 help / color / mirror / Atom feed
From: Greg KH <>
To: Jens Wiklander <>
	"Sumit Garg" <>,
	"Christian König" <>,
	"Rijo Thomas" <>,
	"Devaraj Rangasamy" <>,, "Lars Persson" <>,
	"Patrik Lantz" <>
Subject: Re: [PATCH v2] tee: handle lookup of shm with reference count 0
Date: Wed, 15 Dec 2021 13:52:37 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Dec 15, 2021 at 10:25:01AM +0100, Jens Wiklander wrote:
> Since the tee subsystem does not keep a strong reference to its idle
> shared memory buffers, it races with other threads that try to destroy a
> shared memory through a close of its dma-buf fd or by unmapping the
> memory.
> In tee_shm_get_from_id() when a lookup in teedev->idr has been
> successful, it is possible that the tee_shm is in the dma-buf teardown
> path, but that path is blocked by the teedev mutex. Since we don't have
> an API to tell if the tee_shm is in the dma-buf teardown path or not we
> must find another way of detecting this condition.
> Fix this by doing the reference counting directly on the tee_shm using a
> new refcount_t refcount field. dma-buf is replaced by using
> anon_inode_getfd() instead, this separates the life-cycle of the
> underlying file from the tee_shm. tee_shm_put() is updated to hold the
> mutex when decreasing the refcount to 0 and then remove the tee_shm from
> teedev->idr before releasing the mutex. This means that the tee_shm can
> never be found unless it has a refcount larger than 0.
> Fixes: 967c9cca2cc5 ("tee: generic TEE subsystem")
> Cc:
> Reviewed-by: Lars Persson <>
> Reviewed-by: Sumit Garg <>
> Reported-by: Patrik Lantz <>
> Signed-off-by: Jens Wiklander <>
> ---
> v1->v2
> * fix copyright years in drivers/tee/tee_shm.c
> * update kerneldoc comment for struct tee_shm with the reference counter

Reviewed-by: Greg Kroah-Hartman <>

  reply	other threads:[~2021-12-15 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15  9:25 [PATCH v2] tee: handle lookup of shm with reference count 0 Jens Wiklander
2021-12-15 12:52 ` Greg KH [this message]
2021-12-16 14:56   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).