fsverity: use WARN_ON_ONCE instead of WARN_ON
authorEric Biggers <ebiggers@google.com>
Tue, 28 Mar 2023 04:03:26 +0000 (21:03 -0700)
committerEric Biggers <ebiggers@google.com>
Wed, 12 Apr 2023 02:23:15 +0000 (19:23 -0700)
commit8eb8af4b3df5965dc65a24a32768043f39d82d59
treef680ac37d09ca342cb5598bd8149c8335933f18c
parent1238c8b91c5aca6dd13bccb1b4dc716718e7bfac
fsverity: 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/20230406181542.38894-1-ebiggers@kernel.org
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: Christian Brauner <brauner@kernel.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
fs/verity/enable.c
fs/verity/hash_algs.c
fs/verity/open.c
include/linux/fsverity.h