linux-kernel - [PATCH 0/2] firmware: scm: rework allowlist to be more scalable

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

Message-Id: <20241103-rework-qseecom-v1-0-1d75d4eedc1e@linaro.org>
Date: Sun, 03 Nov 2024 17:37:28 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Bjorn Andersson <andersson@...nel.org>, 
 Konrad Dybcio <konradybcio@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] firmware: scm: rework allowlist to be more scalable

Listing individual devices in the qcom_scm_qseecom_allowlist table
doesn't really scale. For each new device we have to add both DT and an
entry in the table. This way handling new devices by distributions
becomes more complicated: it's not enough to add new DT, the qcom_scm
also has to be patched.

Replace a machine-based allowlist with the platform-based table. If a
particular device has buggy or incompatible firmware, it still can be
disabled in the table. And while the patch to disable it is pending,
make it possible to use qcom_scm.qseecom kernel argument to forcebly
enable or disable usage of QSEECOM.

Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
---
Dmitry Baryshkov (2):
      firmware: qcom: scm: add modparam to control QSEECOM enablement
      firmware: qcom: scm: rework QSEECOM allowlist

 drivers/firmware/qcom/qcom_scm.c | 54 ++++++++++++++++++++++++++--------------
 1 file changed, 36 insertions(+), 18 deletions(-)
---
base-commit: c88416ba074a8913cf6d61b789dd834bbca6681c
change-id: 20241103-rework-qseecom-a6c8ceffc424

Best regards,
-- 
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>