Richard Yao a4de1d38da icp: Use explicit_memset() exclusively in gcm_clear_ctx() ... d634d20d1b had been intended to fix a potential information leak issue where the compiler's optimization passes appeared to remove `memset()` operations that sanitize sensitive data before memory is freed for use by the rest of the kernel. When I wrote it, I had assumed that the compiler would not remove the other `memset()` operations, but upon reflection, I have realized that this was a bad assumption to make. I would rather have a very slight amount of additional overhead when calling `gcm_clear_ctx()` than risk a future compiler remove `memset()` calls. This is likely to happen if someone decides to try doing link time optimization and the person will not think to audit the assembly output for issues like this, so it is best to preempt the possibility before it happens. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Rob Norris <robn@despairlabs.com> Reviewed-by: Alexander Motin <mav@FreeBSD.org> Reviewed-by: Jorgen Lundman <lundman@lundman.net> Signed-off-by: Richard Yao <richard@ryao.dev> Closes #17343 (cherry picked from commit d8a33bc0a5)		2025-05-28 16:00:28 -07:00
..
ccm.c	SPDX: license tags: CDDL-1.0	2025-04-16 09:59:44 -07:00
gcm_generic.c	SPDX: license tags: CDDL-1.0	2025-04-16 09:59:44 -07:00
gcm_pclmulqdq.c	SPDX: license tags: CDDL-1.0	2025-04-16 09:59:44 -07:00
gcm.c	gcm_avx_init: zero the ghash state after hashing the IV	2025-04-16 09:59:45 -07:00
modes.c	icp: Use explicit_memset() exclusively in gcm_clear_ctx()	2025-05-28 16:00:28 -07:00