diff options
author | 2023-01-13 19:52:11 +0800 | |
---|---|---|
committer | 2023-01-30 12:51:54 +0000 | |
commit | 3288666c72568fe1cc7f5c5ae33dfd3ab18004c8 (patch) | |
tree | be3af6c5f73e396fe2786fd7c1359bdc9a161f41 /scripts/lib/kdoc/kdoc_files.py | |
parent | fscache: Use wait_on_bit() to wait for the freeing of relinquished volume (diff) | |
download | wireguard-linux-3288666c72568fe1cc7f5c5ae33dfd3ab18004c8.tar.xz wireguard-linux-3288666c72568fe1cc7f5c5ae33dfd3ab18004c8.zip |
fscache: Use clear_and_wake_up_bit() in fscache_create_volume_work()
fscache_create_volume_work() uses wake_up_bit() to wake up the processes
which are waiting for the completion of volume creation. According to
comments in wake_up_bit() and waitqueue_active(), an extra smp_mb() is
needed to guarantee the memory order between FSCACHE_VOLUME_CREATING
flag and waitqueue_active() before invoking wake_up_bit().
Fixing it by using clear_and_wake_up_bit() to add the missing memory
barrier.
Reviewed-by: Jingbo Xu <jefflexu@linux.alibaba.com>
Signed-off-by: Hou Tao <houtao1@huawei.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Link: https://lore.kernel.org/r/20230113115211.2895845-3-houtao@huaweicloud.com/ # v3
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions