a6d0dbba - lib/crc: remove unnecessary prompt for CONFIG_CRC_T10DIF

Tue, 01 Apr 2025 22:15:57 +0000

lib/crc: remove unnecessary prompt for CONFIG_CRC_T10DIFAll modules that need CONFIG_CRC_T10DIF already select it, so there is noneed to bother users about the option.Reviewed-by: Christoph Hellwig Reviewed-by: "Martin K. Petersen" Acked-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20250401221600.24878-5-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux-6.15/arch/mips/configs/ip30_defconfig

2890601f - crypto: vmac - remove unused VMAC algorithm

Thu, 26 Dec 2024 19:43:08 +0000

crypto: vmac - remove unused VMAC algorithmRemove the vmac64 template, as it has no known users. It also continuesto have longstanding bugs such as alignment violations (seehttps://lore.kernel.org/r/20241226134847.6690-1-evepolonium@gmail.com/).This code was added in 2009 by commit f1939f7c5645 ("crypto: vmac - Newhash algorithm for intel_txt support"). Based on the mention ofintel_txt support in the commit title, it seems it was added as aprerequisite for the contemporaneous patch"intel_txt: add s3 userspace memory integrity verification"(https://lore.kernel.org/r/4ABF2B50.6070106@intel.com/). In the designproposed by that patch, when an Intel Trusted Execution Technology (TXT)enabled system resumed from suspend, the "tboot" trusted executablelaunched the Linux kernel without verifying userspace memory, and thenthe Linux kernel used VMAC to verify userspace memory.However, that patch was never merged, as reviewers had objected to thedesign. It was later reworked into commit 4bd96a7a8185 ("x86, tboot:Add support for S3 memory integrity protection") which made tboot verifythe memory instead. Thus the VMAC support in Linux was never used.No in-tree user has appeared since then, other than potentially theusual components that allow specifying arbitrary hash algorithms byname, namely AF_ALG and dm-integrity. However there are no indicationsthat VMAC is being used with these components. Debian Code Search andweb searches for "vmac64" (the actual algorithm name) do not return anyresults other than the kernel itself, suggesting that it does not appearin any other code or documentation. Explicitly grepping the source codeof the usual suspects (libell, iwd, cryptsetup) finds no matches either.Before 2018, the vmac code was also completely broken due to using ahardcoded nonce and the wrong endianness for the MAC. It was then fixedby commit ed331adab35b ("crypto: vmac - add nonced version with bigendian digest") and commit 0917b873127c ("crypto: vmac - remove insecureversion with hardcoded nonce"). These were intentionally breakingchanges that changed all the computed MAC values as well as thealgorithm name ("vmac" to "vmac64"). No complaints were ever receivedabout these breaking changes, strongly suggesting the absence of users.The reason I had put some effort into fixing this code in 2018 isbecause it was used by an out-of-tree driver. But if it is still neededin that particular out-of-tree driver, the code can be carried in thatdriver instead. There is no need to carry it upstream.Cc: Atharva Tiwari Cc: Shane Wang Signed-off-by: Eric Biggers Acked-by: Ard Biesheuvel Acked-by: Geert Uytterhoeven # m68kSigned-off-by: Herbert Xu List of files: /linux-6.15/arch/mips/configs/ip30_defconfig

bb2d6350 - MIPS: config: Add ip30_defconfig

Sun, 14 Jul 2024 02:20:50 +0000

MIPS: config: Add ip30_defconfigAdd ip30_defconfig derived from ip27_defconfig to ensure thistarget is build tested by various kernel testing projects.Signed-off-by: Jiaxun Yang Signed-off-by: Thomas Bogendoerfer List of files: /linux-6.15/arch/mips/configs/ip30_defconfig

Changes in ip30_defconfig

a6d0dbba - lib/crc: remove unnecessary prompt for CONFIG_CRC_T10DIF

2890601f - crypto: vmac - remove unused VMAC algorithm

bb2d6350 - MIPS: config: Add ip30_defconfig