linux-kernel - Re: [PATCH v5 4/4] firmware: arm_scmi: optee: use optee system invocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20230322164007.hjsjifg4wznxkgdz@bogus>
Date:   Wed, 22 Mar 2023 16:40:07 +0000
From:   Sudeep Holla <sudeep.holla@....com>
To:     Etienne Carriere <etienne.carriere@...aro.org>
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        op-tee@...ts.trustedfirmware.org,
        Sumit Garg <sumit.garg@...aro.org>,
        Jens Wiklander <jens.wiklander@...aro.org>,
        Cristian Marussi <cristian.marussi@....com>
Subject: Re: [PATCH v5 4/4] firmware: arm_scmi: optee: use optee system
 invocation

On Mon, Mar 20, 2023 at 05:28:01PM +0100, Etienne Carriere wrote:
> Changes SCMI optee transport to call tee_client_system_session()
> to request optee driver to provision an entry context in OP-TEE
> for processing OP-TEE messages. This prevents possible deadlock
> in case OP-TEE threads are all consumed while these may be waiting
> for a clock or regulator to be enable which SCMI OP-TEE service which
> requires a free thread context to execute.
>

Assuming it will be routed via OPTEE tree,

Acked-by: Sudeep Holla <sudeep.holla@....com>

-- 
Regards,
Sudeep