diff options
| author | Tetsuo Handa <[email protected]> | 2022-02-11 07:15:54 +0000 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2022-02-11 12:51:23 +0000 |
| commit | bf23747ee05320903177809648002601cd140cdd (patch) | |
| tree | d1b844e3b71e140d283aa7c474ed978b90b00d65 /lib/mpi/mpi-bit.c | |
| parent | Merge tag 'nvme-5.17-2022-02-10' of git://git.infradead.org/nvme into block-5.17 (diff) | |
| download | kernel-bf23747ee05320903177809648002601cd140cdd.tar.gz kernel-bf23747ee05320903177809648002601cd140cdd.zip | |
loop: revert "make autoclear operation asynchronous"
The kernel test robot is reporting that xfstest which does
umount ext2 on xfs
umount xfs
sequence started failing, for commit 322c4293ecc58110 ("loop: make
autoclear operation asynchronous") removed a guarantee that fput() of
backing file is processed before lo_release() from close() returns to
user mode.
And syzbot is reporting that deferring destroy_workqueue() from
__loop_clr_fd() to a WQ context did not help [1]. Revert that commit.
Link: https://syzkaller.appspot.com/bug?extid=831661966588c802aae9 [1]
Reported-by: kernel test robot <[email protected]>
Acked-by: Jan Kara <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Reported-by: syzbot <[email protected]>
Signed-off-by: Tetsuo Handa <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'lib/mpi/mpi-bit.c')
0 files changed, 0 insertions, 0 deletions