diff options
author | 2021-06-28 19:35:44 -0700 | |
---|---|---|
committer | 2021-06-29 10:53:47 -0700 | |
commit | 592fa002180af3425ba962b8e74edd680f0ec77b (patch) | |
tree | 66bed02c0252d8629f4e85b5fa003e7cae40e420 /mm/backing-dev.c | |
parent | writeback, cgroup: do not switch inodes with I_WILL_FREE flag (diff) | |
download | wireguard-linux-592fa002180af3425ba962b8e74edd680f0ec77b.tar.xz wireguard-linux-592fa002180af3425ba962b8e74edd680f0ec77b.zip |
writeback, cgroup: add smp_mb() to cgroup_writeback_umount()
A full memory barrier is required between clearing SB_ACTIVE flag in
generic_shutdown_super() and checking isw_nr_in_flight in
cgroup_writeback_umount(), otherwise a new switch operation might be
scheduled after atomic_read(&isw_nr_in_flight) returned 0. This would
result in a non-flushed isw_wq, and a potential crash.
The problem hasn't yet been seen in the real life and was discovered by
Jan Kara by looking into the code.
Link: https://lkml.kernel.org/r/20210608230225.2078447-3-guro@fb.com
Signed-off-by: Roman Gushchin <guro@fb.com>
Suggested-by: Jan Kara <jack@suse.cz>
Reviewed-by: Jan Kara <jack@suse.cz>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Dave Chinner <dchinner@redhat.com>
Cc: Dennis Zhou <dennis@kernel.org>
Cc: Jan Kara <jack@suse.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/backing-dev.c')
0 files changed, 0 insertions, 0 deletions