Re: [f2fs-dev] [PATCH 1/2] f2fs: fix race in concurrent f2fs_stop_gc_thread

2024-11-03 Thread Long Li via Linux-f2fs-devel
On Fri, Nov 01, 2024 at 10:56:59AM +0800, Chao Yu wrote: > On 2024/10/31 14:45, Long Li wrote: > > In my test case, concurrent calls to f2fs shutdown report the following > > stack trace: > > > > Oops: general protection fault, probably for non-canonical address > > 0xc6cfff63bb5513fc: [#1

[f2fs-dev] [PATCH v2] f2fs: fix race in concurrent f2fs_stop_gc_thread

2024-11-03 Thread Long Li via Linux-f2fs-devel
In my test case, concurrent calls to f2fs shutdown report the following stack trace: Oops: general protection fault, probably for non-canonical address 0xc6cfff63bb5513fc: [#1] PREEMPT SMP PTI CPU: 0 UID: 0 PID: 678 Comm: f2fs_rep_shutdo Not tainted 6.12.0-rc5-next-20241029-g6fb2fa9805c5-

[f2fs-dev] [PATCH 1/2] f2fs: fix race in concurrent f2fs_stop_gc_thread

2024-10-30 Thread Long Li via Linux-f2fs-devel
In my test case, concurrent calls to f2fs shutdown report the following stack trace: Oops: general protection fault, probably for non-canonical address 0xc6cfff63bb5513fc: [#1] PREEMPT SMP PTI CPU: 0 UID: 0 PID: 678 Comm: f2fs_rep_shutdo Not tainted 6.12.0-rc5-next-20241029-g6fb2fa9805c5-

[f2fs-dev] [PATCH 2/2] Revert "f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()"

2024-10-30 Thread Long Li via Linux-f2fs-devel
This reverts commit c7f114d864ac91515bb07ac271e9824a20f5ed95. The race conditions between concurrent f2fs_stop_gc_thread() calls are now protected by a dedicated lock, making the additional s_umount lock protection unnecessary. Therefore, revert this patch. Signed-off-by: Long Li --- fs/f2fs/f2