| 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
| ||
|
Message-ID: <ff5b7c88eea8b126ed76029fb57254f29542aa22.1739976486.git.geert+renesas@glider.be> Date: Wed, 19 Feb 2025 15:48:24 +0100 From: Geert Uytterhoeven <geert+renesas@...der.be> To: Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>, Robin Murphy <robin.murphy@....com> Cc: iommu@...ts.linux.dev, linux-kernel@...r.kernel.org, Geert Uytterhoeven <geert+renesas@...der.be> Subject: [PATCH] iommu: Spelling s/KConfig/Kconfig/ Fix two misspellings of "Kconfig". Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be> --- drivers/iommu/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig index 6cfd1b5b6e07f038..6c46e1d58987cd11 100644 --- a/drivers/iommu/Kconfig +++ b/drivers/iommu/Kconfig @@ -348,14 +348,14 @@ config ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT an iommu domain will report an abort back to the device and will not be allowed to pass through the SMMU. - Any old kernels that existed before this KConfig was + Any old kernels that existed before this Kconfig was introduced would default to _allowing_ bypass (AKA the equivalent of NO for this config). However the default for this option is YES because the old behavior is insecure. There are few reasons to allow unmatched stream bypass, and even fewer good ones. If saying YES here breaks your board - you should work on fixing your board. This KConfig option + you should work on fixing your board. This Kconfig option is expected to be removed in the future and we'll simply hardcode the bypass disable in the code. -- 2.43.0
Powered by blists - more mailing lists