Eric Biggers 41b2ad80fd fscrypt: use WARN_ON_ONCE instead of WARN_ON ... As per Linus's suggestion (https://lore.kernel.org/r/CAHk-=whefxRGyNGzCzG6BVeM=5vnvgb-XhSeFJVxJyAxAF8XRA@mail.gmail.com), use WARN_ON_ONCE instead of WARN_ON. This barely adds any extra overhead, and it makes it so that if any of these ever becomes reachable (they shouldn't, but that's the point), the logs can't be flooded. Link: https://lore.kernel.org/r/20230320233943.73600-1-ebiggers@kernel.org Signed-off-by: Eric Biggers <ebiggers@google.com>		2023-03-27 21:15:50 -07:00
..
Kconfig	fscrypt: relax Kconfig dependencies for crypto API algorithms	2021-04-22 17:31:32 +10:00
Makefile	fscrypt: add inline encryption support	2020-07-08 10:29:30 -07:00
bio.c	fscrypt: use WARN_ON_ONCE instead of WARN_ON	2023-03-27 21:15:50 -07:00
crypto.c	fscrypt: support decrypting data from large folios	2023-01-28 15:10:12 -08:00
fname.c	fscrypt: use WARN_ON_ONCE instead of WARN_ON	2023-03-27 21:15:50 -07:00
fscrypt_private.h	fscrypt: use WARN_ON_ONCE instead of WARN_ON	2023-03-27 21:15:50 -07:00
hkdf.c	fscrypt: use WARN_ON_ONCE instead of WARN_ON	2023-03-27 21:15:50 -07:00
hooks.c	fscrypt: use WARN_ON_ONCE instead of WARN_ON	2023-03-27 21:15:50 -07:00
inline_crypt.c	blk-crypto: add a blk_crypto_config_supported_natively helper	2022-11-21 11:39:05 -07:00
keyring.c	fscrypt: use WARN_ON_ONCE instead of WARN_ON	2023-03-27 21:15:50 -07:00
keysetup.c	fscrypt: use WARN_ON_ONCE instead of WARN_ON	2023-03-27 21:15:50 -07:00
keysetup_v1.c	fscrypt: stop holding extra request_queue references	2022-09-21 20:33:06 -07:00
policy.c	fscrypt: use WARN_ON_ONCE instead of WARN_ON	2023-03-27 21:15:50 -07:00