summaryrefslogtreecommitdiffstats
path: root/kernel/fork.c
diff options
context:
space:
mode:
authorRyusuke Konishi <konishi.ryusuke@gmail.com>2023-12-07 13:57:30 +0900
committerAndrew Morton <akpm@linux-foundation.org>2023-12-20 15:02:58 -0800
commit2c20b0f26694e1d40bb9b86f8eff5675e87003d1 (patch)
tree11e8da95b14e609fa7bfe3db659e06cb27a8a781 /kernel/fork.c
parent6915f40c3a43740207f7af70bab96c20eed22aa3 (diff)
downloadlinux-stable-2c20b0f26694e1d40bb9b86f8eff5675e87003d1.tar.gz
linux-stable-2c20b0f26694e1d40bb9b86f8eff5675e87003d1.tar.bz2
linux-stable-2c20b0f26694e1d40bb9b86f8eff5675e87003d1.zip
nilfs2: switch WARN_ONs to warning output in nilfs_sufile_do_free()
nilfs_sufile_do_free(), which is called when log write fails or during GC, uses WARN_ONs to check for abnormal status of metadata. In the former case, these WARN_ONs will not be fired, but in the latter case they don't "never-happen". It is possible to trigger these by intentionally modifying the userland GC library to release segments that are not in the expected state. So, replace them with warning output using the dedicated macro nilfs_warn(). This replaces two potentially triggered WARN_ONs with ones that use a warning output macro. Link: https://lkml.kernel.org/r/20231207045730.5205-1-konishi.ryusuke@gmail.com Signed-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'kernel/fork.c')
0 files changed, 0 insertions, 0 deletions