linux-kernel - Re: [PATCH v3] firmware: qcom_scm: use 64-bit calling convention only when client is 64-bit

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: <169586125040.1226038.6973458146206642205.b4-ty@kernel.org>
Date:   Wed, 27 Sep 2023 17:34:10 -0700
From:   Bjorn Andersson <andersson@...nel.org>
To:     Andy Gross <agross@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        Elliot Berman <quic_eberman@...cinc.com>,
        Kathiravan Thirumoorthy <quic_kathirav@...cinc.com>
Cc:     linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org
Subject: Re: [PATCH v3] firmware: qcom_scm: use 64-bit calling convention only when client is 64-bit


On Mon, 25 Sep 2023 13:59:22 +0530, Kathiravan Thirumoorthy wrote:
> Per the "SMC calling convention specification", the 64-bit calling
> convention can only be used when the client is 64-bit. Whereas the
> 32-bit calling convention can be used by either a 32-bit or a 64-bit
> client.
> 
> Currently during SCM probe, irrespective of the client, 64-bit calling
> convention is made, which is incorrect and may lead to the undefined
> behaviour when the client is 32-bit. Let's fix it.
> 
> [...]

Applied, thanks!

[1/1] firmware: qcom_scm: use 64-bit calling convention only when client is 64-bit
      commit: 3337a6fea25370d3d244ec6bb38c71ee86fcf837

Best regards,
-- 
Bjorn Andersson <andersson@...nel.org>