From: Sumit Garg <sumit.garg@kernel.org>
To: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
Cc: "Jens Wiklander" <jens.wiklander@linaro.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Apurupa Pattapu" <quic_apurupa@quicinc.com>,
"Kees Cook" <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 01/11] tee: allow a driver to allocate a tee_device without a pool
Date: Mon, 21 Apr 2025 15:48:48 +0530 [thread overview]
Message-ID: <aAYbiAOyYkYob3rU@sumit-X1> (raw)
In-Reply-To: <20250327-qcom-tee-using-tee-ss-without-mem-obj-v3-1-7f457073282d@oss.qualcomm.com>
On Thu, Mar 27, 2025 at 07:47:23PM -0700, Amirreza Zarrabi wrote:
> A TEE driver doesn't always need to provide a pool if it doesn't
> support memory sharing ioctls and can allocate memory for TEE
> messages in another way. Although this is mentioned in the
> documentation for tee_device_alloc(), it is not handled correctly.
>
> Signed-off-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
> ---
> drivers/tee/tee_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
-Sumit
> diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c
> index d113679b1e2d..24edce4cdbaa 100644
> --- a/drivers/tee/tee_core.c
> +++ b/drivers/tee/tee_core.c
> @@ -888,7 +888,7 @@ struct tee_device *tee_device_alloc(const struct tee_desc *teedesc,
>
> if (!teedesc || !teedesc->name || !teedesc->ops ||
> !teedesc->ops->get_version || !teedesc->ops->open ||
> - !teedesc->ops->release || !pool)
> + !teedesc->ops->release)
> return ERR_PTR(-EINVAL);
>
> teedev = kzalloc(sizeof(*teedev), GFP_KERNEL);
>
> --
> 2.34.1
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Sumit Garg <sumit.garg@kernel.org>
To: op-tee@lists.trustedfirmware.org
Subject: Re: [PATCH v3 01/11] tee: allow a driver to allocate a tee_device without a pool
Date: Mon, 21 Apr 2025 15:48:48 +0530 [thread overview]
Message-ID: <aAYbiAOyYkYob3rU@sumit-X1> (raw)
In-Reply-To: <<20250327-qcom-tee-using-tee-ss-without-mem-obj-v3-1-7f457073282d@oss.qualcomm.com>>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Thu, Mar 27, 2025 at 07:47:23PM -0700, Amirreza Zarrabi wrote:
> A TEE driver doesn't always need to provide a pool if it doesn't
> support memory sharing ioctls and can allocate memory for TEE
> messages in another way. Although this is mentioned in the
> documentation for tee_device_alloc(), it is not handled correctly.
>
> Signed-off-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
> ---
> drivers/tee/tee_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
-Sumit
> diff --git a/drivers/tee/tee_core.c b/drivers/tee/tee_core.c
> index d113679b1e2d..24edce4cdbaa 100644
> --- a/drivers/tee/tee_core.c
> +++ b/drivers/tee/tee_core.c
> @@ -888,7 +888,7 @@ struct tee_device *tee_device_alloc(const struct tee_desc *teedesc,
>
> if (!teedesc || !teedesc->name || !teedesc->ops ||
> !teedesc->ops->get_version || !teedesc->ops->open ||
> - !teedesc->ops->release || !pool)
> + !teedesc->ops->release)
> return ERR_PTR(-EINVAL);
>
> teedev = kzalloc(sizeof(*teedev), GFP_KERNEL);
>
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2025-04-21 10:18 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 2:47 [PATCH v3 00/11] Trusted Execution Environment (TEE) driver for Qualcomm TEE (QTEE) Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 01/11] tee: allow a driver to allocate a tee_device without a pool Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-04-21 10:18 ` Sumit Garg [this message]
2025-04-21 10:18 ` Sumit Garg
2025-03-28 2:47 ` [PATCH v3 02/11] tee: add close_context to TEE driver operation Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-04-07 14:55 ` Jens Wiklander
2025-04-07 14:55 ` Jens Wiklander
2025-04-09 0:20 ` Amirreza Zarrabi
2025-04-09 0:20 ` Amirreza Zarrabi
2025-04-21 10:42 ` Sumit Garg
2025-04-21 10:42 ` Sumit Garg
2025-04-28 4:01 ` Amirreza Zarrabi
2025-04-28 4:01 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 03/11] tee: add TEE_IOCTL_PARAM_ATTR_TYPE_UBUF Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-03-29 4:58 ` kernel test robot
2025-03-29 4:58 ` kernel test robot
2025-04-08 12:19 ` Jens Wiklander
2025-04-08 12:19 ` Jens Wiklander
2025-03-28 2:47 ` [PATCH v3 04/11] tee: add TEE_IOCTL_PARAM_ATTR_TYPE_OBJREF Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-04-21 13:38 ` Sumit Garg
2025-04-21 13:38 ` Sumit Garg
2025-04-28 4:17 ` Amirreza Zarrabi
2025-04-28 4:17 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 05/11] firmware: qcom: scm: add support for object invocation Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 06/11] firmware: qcom: scm: remove unused arguments to the shm_brige Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 07/11] firmware: qcom: tzmem: export shm_bridge create/delete Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 08/11] tee: add Qualcomm TEE driver Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-03-28 22:21 ` kernel test robot
2025-03-28 22:21 ` kernel test robot
2025-04-08 12:47 ` Jens Wiklander
2025-04-08 12:47 ` Jens Wiklander
2025-04-09 1:26 ` Amirreza Zarrabi
2025-04-09 1:26 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 09/11] qcomtee: add primordial object Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 10/11] qcomtee: enable TEE_IOC_SHM_ALLOC ioctl Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-03-28 2:47 ` [PATCH v3 11/11] Documentation: tee: Add Qualcomm TEE driver Amirreza Zarrabi
2025-03-28 2:47 ` Amirreza Zarrabi
2025-04-09 8:30 ` [PATCH v3 00/11] Trusted Execution Environment (TEE) driver for Qualcomm TEE (QTEE) neil.armstrong
2025-04-09 8:30 ` neil.armstrong
2025-04-11 5:55 ` Amirreza Zarrabi
2025-04-11 5:55 ` Amirreza Zarrabi
[not found] < <CAHUa44GRBiRr6CsFWxJhyzf1cRSEP66m5K7uFntOv3oYWTHWgQ@mail.gmail.com>
2025-04-09 0:28 ` [PATCH v3 03/11] tee: add TEE_IOCTL_PARAM_ATTR_TYPE_UBUF Amirreza Zarrabi
2025-04-09 0:28 ` Amirreza Zarrabi
2025-04-09 6:41 ` Jens Wiklander
2025-04-09 6:41 ` Jens Wiklander
2025-04-09 7:20 ` Amirreza Zarrabi
2025-04-09 7:20 ` Amirreza Zarrabi
2025-04-09 8:27 ` Jens Wiklander
2025-04-09 8:27 ` Jens Wiklander
2025-04-21 13:17 ` Sumit Garg
2025-04-21 13:17 ` Sumit Garg
2025-04-28 4:37 ` Amirreza Zarrabi
2025-04-28 4:37 ` Amirreza Zarrabi
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=aAYbiAOyYkYob3rU@sumit-X1 \
--to=sumit.garg@kernel.org \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavoars@kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=kees@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=quic_apurupa@quicinc.com \
--cc=sumit.semwal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.