diff options
| author | Eric Biggers <[email protected]> | 2023-03-20 16:39:43 -0700 |
|---|---|---|
| committer | Eric Biggers <[email protected]> | 2023-03-27 21:15:50 -0700 |
| commit | 41b2ad80fdcaafd42fce173cb95847d0cd8614c2 (patch) | |
| tree | 633980d206be0ae2ce7215bd46207b0a5a1cf02e /scripts/gdb/linux | |
| parent | 6f2656eab290f0dd437cd4b2ec956c3519172d3b (diff) | |
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/[email protected]
Signed-off-by: Eric Biggers <[email protected]>
Diffstat (limited to 'scripts/gdb/linux')
0 files changed, 0 insertions, 0 deletions