On Tue, Oct 26, 2021 at 10:56 AM Daeho Jeong <[email protected]> wrote: > > > Yes, I doubt the problem may also happen in f2fs_evict_inode() with below > > callpath: > > > > - evict_inode > > - dquot_initialize failed > > - sb_start_intwrite > > - f2fs_truncate > > - dquot_initialize lock dqio_sem > > > > How about this? > > > > Got it~ > Then we need this in both f2fs_evict_inode() and f2fs_drop_inode(). >
It turns out this deadlock issue was related to the Android kernel only. :( That was related to one of Android tracepoints, which triggered internal memory reclaim inside of it. We made a workaround for that in Android kernel. Thanks, _______________________________________________ Linux-f2fs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
