On Thu, 21 Mar 2024 17:29:03 -0700 Jaegeuk Kim
>
> I posted this patch before Light reported.
Yeah, his report's timestamp is 2024-03-20 6:59, nearly 7 hours later,
which shows that you constructed the deadlock with nothing to do with
his report.
>
> And, in the report, I didn't get this:
>
On 03/22, Hillf Danton wrote:
> On Tue, 19 Mar 2024 17:14:42 -0700 Jaegeuk Kim
> > f2fs_ioc_shutdown(F2FS_GOING_DOWN_NOSYNC) issue_discard_thread
> > - mnt_want_write_file()
> >- sb_start_write(SB_FREEZE_WRITE)
>__sb_start_write()
> percpu_down_read()
> >
On Tue, 19 Mar 2024 17:14:42 -0700 Jaegeuk Kim
> f2fs_ioc_shutdown(F2FS_GOING_DOWN_NOSYNC) issue_discard_thread
> - mnt_want_write_file()
>- sb_start_write(SB_FREEZE_WRITE)
__sb_start_write()
percpu_down_read()
> -
>
On 2024/3/20 8:14, Jaegeuk Kim wrote:
f2fs_ioc_shutdown(F2FS_GOING_DOWN_NOSYNC) issue_discard_thread
- mnt_want_write_file()
- sb_start_write(SB_FREEZE_WRITE)
- sb_start_intwrite(SB_FREEZE_FS);
- f2fs_stop_checkpoint(sbi, false,:
f2fs_ioc_shutdown(F2FS_GOING_DOWN_NOSYNC) issue_discard_thread
- mnt_want_write_file()
- sb_start_write(SB_FREEZE_WRITE)
- sb_start_intwrite(SB_FREEZE_FS);
- f2fs_stop_checkpoint(sbi, false,: waiting
STOP_CP_REASON_SHUTDOWN);
-
