mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harshal Dev <harshal.dev@oss.qualcomm.com>
To: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
Cc: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>,
	Basant Kumar <basantk@qti.qualcomm.com>,
	Apurupa Pattapu <apurupa@qti.qualcomm.com>,
	Arun Kumar Neelakantam <aneelaka@qti.qualcomm.com>,
	op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	Sumit Garg <sumit.garg@oss.qualcomm.com>,
	Jens Wiklander <jens.wiklander@oss.qualcomm.com>,
	Sumit Garg <sumit.garg@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v5 3/7] tee: qcomtee: Allow object invokes from kernel clients
Date: Mon, 2 Nov 2026 19:11:27 +0530	[thread overview]
Message-ID: <e618a9f3-6a33-4dbc-a15f-217542ef28f9@oss.qualcomm.com> (raw)
In-Reply-To: <952816ce-3e37-4628-8308-4208b4359549@oss.qualcomm.com>

Hi Amir,

On 26-10-2026 08:45 am, Amirreza Zarrabi wrote:
> Hi Harshal,
> 
> On 10/15/2026 10:39 PM, Harshal Dev wrote:
>> From: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
>>
>> QCOMTEE currently treats UBUF parameters as userspace addresses and
>> applies userspace restrictions when invoking the root object. This is
>> not suitable for object invocation requests issued by kernel clients.
>>
>> Use the kernel_ctx flag to distinguish kernel client requests from
>> userspace requests. For kernel contexts, do not mark UBUF parameters as
>> user addresses, and allow permitted root-object operations to proceed
>> without applying the userspace-only checks.
>>
>> This allows in-kernel users of tee_client_object_invoke_func() to issue
>> object invocation requests through the qcomtee backend.
>>
>> Co-developed-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>> Acked-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
>> Reviewed-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
>> Signed-off-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
> 
> Same here.
>

Ack.

Regards,
Harshal
 
> - Amir

  reply	other threads:[~2026-11-02 13:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 11:39 [PATCH v5 0/7] Add TEE based client driver for UEFI Secure Application Harshal Dev
2026-10-15 11:39 ` [PATCH v5 1/7] tee: qcomtee: Track the object invocation context Harshal Dev
2026-10-16 12:53   ` Kuldeep Singh
2026-10-15 11:39 ` [PATCH v5 2/7] tee: Add kernel client object invoke helper Harshal Dev
2026-10-16 12:54   ` Kuldeep Singh
2026-10-26  3:09   ` Amirreza Zarrabi
2026-11-02 13:40     ` Harshal Dev
2026-10-15 11:39 ` [PATCH v5 3/7] tee: qcomtee: Allow object invokes from kernel clients Harshal Dev
2026-10-16 12:55   ` Kuldeep Singh
2026-10-26  3:15   ` Amirreza Zarrabi
2026-11-02 13:41     ` Harshal Dev [this message]
2026-10-15 11:39 ` [PATCH v5 4/7] tee: Export uuidv5 generation for TEE backends Harshal Dev
2026-10-16 12:55   ` Kuldeep Singh
2026-10-15 11:39 ` [PATCH v5 5/7] tee: qcomtee: Add support for registering QTEE services on TEE bus Harshal Dev
2026-10-16 12:56   ` Kuldeep Singh
2026-10-26  3:51   ` Amirreza Zarrabi
2026-11-02 13:44     ` Harshal Dev
2026-10-15 11:39 ` [PATCH v5 6/7] firmware: qcom: Add support for TEE based EFI-var client driver Harshal Dev
2026-10-26  4:44   ` Amirreza Zarrabi
2026-10-15 11:39 ` [PATCH v5 7/7] arm64: defconfig: Enable UefiSecApp TEE client driver for Qualcomm SoCs Harshal Dev

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=e618a9f3-6a33-4dbc-a15f-217542ef28f9@oss.qualcomm.com \
    --to=harshal.dev@oss.qualcomm.com \
    --cc=amirreza.zarrabi@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=aneelaka@qti.qualcomm.com \
    --cc=apurupa@qti.qualcomm.com \
    --cc=basantk@qti.qualcomm.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=jens.wiklander@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuldeep.singh@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.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

all inboxes | Powered by JetHome®