summaryrefslogtreecommitdiff
path: root/include/linux/net/intel
diff options
context:
space:
mode:
authorJulian Braha <julianbraha@gmail.com>2026-09-04 12:09:11 +0100
committerMimi Zohar <zohar@linux.ibm.com>2026-09-04 14:01:00 -0400
commit6903878d4654bdef4e08e38cdf1ae306ce7de5f9 (patch)
treea10eead6fc92f47f7eccaade042f099e9bd4a8e1 /include/linux/net/intel
parent8861f6d5c0678a7c5089c7b272509fc5931b8437 (diff)
downloadlinux-6903878d4654bdef4e08e38cdf1ae306ce7de5f9.tar.gz
linux-6903878d4654bdef4e08e38cdf1ae306ce7de5f9.zip
ima: allow users to specify the pcr index with IMA_MEASURE_PCR_IDX
The IMA_MEASURE_PCR_IDX option is currently not visible in the kconfig frontend, so it always uses its default, 10. This means that the 'range 8 14' is dead code, and users are unable to specify the pcr index value. In a previous discussion, Mimi explained that users should be able to use this config option to specify the pcr index. [1] Let's add a prompt for users to specify the pcr index, when EXPERT is enabled. This dead range was found by kconfirm, a static analysis tool for Kconfig. Link: https://lore.kernel.org/all/1feff118-4afa-4b9c-86f1-271a7a88208f@gmail.com/T/#mc4efa2491b4937eb7c9e532c29ffba516a70e662 [1] Signed-off-by: Julian Braha <julianbraha@gmail.com> Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'include/linux/net/intel')
0 files changed, 0 insertions, 0 deletions