linux-kernel - Re: [REGRESSION] firmware: qcom: scm: smc: switch to using the SCM allocator

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <68b0476f-dfa1-44cb-a01a-f4afbaaa98e5@gmail.com>
Date: Sat, 7 Sep 2024 01:49:02 -0700
From: Rudraksha Gupta <guptarud@...il.com>
To: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Cc: regressions@...ts.linux.dev, brgl@...ev.pl, andersson@...nel.org,
 konrad.dybcio@...aro.org, robh@...nel.org, krzk+dt@...nel.org,
 conor+dt@...nel.org, robimarko@...il.com, quic_gurus@...cinc.com,
 luzmaximilian@...il.com, catalin.marinas@....com, will@...nel.org,
 srinivas.kandagatla@...aro.org, arnd@...db.de, quic_eberman@...cinc.com,
 elder@...nel.org, linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 kernel@...cinc.com, ahalaney@...hat.com, quic_djaggi@...cinc.com
Subject: Re: [REGRESSION] firmware: qcom: scm: smc: switch to using the SCM
 allocator

> Looks like qcom_scm_get_tzmem_pool() returns NULL. Not sure how this
> happens. Can you confirm that the QCom SCM driver probed correctly?

Thanks for looking into this! Please let me know how I can help!


I've been building the driver into the kernel I believe. Here's the 
relevant line in the config:

$ rg -i "scm"
samsung/expressatt/linux.defconfig
1615:# CONFIG_ARM_SCMI_PROTOCOL is not set
1627:CONFIG_QCOM_SCM=y
1628:# CONFIG_QCOM_SCM_DOWNLOAD_MODE_DEFAULT is not set


It seems like the scm driver is being probed:

~ # dmesg | grep scm
[    0.066438] qcom_scm: convention: smc legacy
[    0.362543] bus: 'platform': add driver qcom_scm


Also here is the complete dmesg output (Had to paste in pastebin as it 
made the email bigger than 100 KB):

https://pastebin.com/4iWKvZ8z