aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strncpy-src.c
diff options
context:
space:
mode:
authorEric Biggers <[email protected]>2023-03-27 21:03:26 -0700
committerEric Biggers <[email protected]>2023-04-11 19:23:15 -0700
commit8eb8af4b3df5965dc65a24a32768043f39d82d59 (patch)
treef680ac37d09ca342cb5598bd8149c8335933f18c /lib/test_fortify/write_overflow-strncpy-src.c
parent1238c8b91c5aca6dd13bccb1b4dc716718e7bfac (diff)
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/[email protected] Reviewed-by: Chaitanya Kulkarni <[email protected]> Reviewed-by: Christian Brauner <[email protected]> Signed-off-by: Eric Biggers <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions