Re: [PATCH] f2fs: protect new segment allocation in expand_inode_data

2020-06-03 Thread Daeho Jeong
Oh, thanks for notification! 2020년 6월 3일 (수) 오후 3:59, Chao Yu 님이 작성: > > On 2020/6/1 11:03, Daeho Jeong wrote: > > From: Daeho Jeong > > > > Found a new segemnt allocation without f2fs_lock_op() in > > expand_inode_data(). So, when we do fallocate() for a pinned file > > and trigger checkpoint ve

Re: [PATCH] f2fs: protect new segment allocation in expand_inode_data

2020-06-02 Thread Chao Yu
On 2020/6/1 11:03, Daeho Jeong wrote: > From: Daeho Jeong > > Found a new segemnt allocation without f2fs_lock_op() in > expand_inode_data(). So, when we do fallocate() for a pinned file > and trigger checkpoint very frequently and simultaneously. F2FS gets > stuck in the below code of do_checkpo

[PATCH] f2fs: protect new segment allocation in expand_inode_data

2020-05-31 Thread Daeho Jeong
From: Daeho Jeong Found a new segemnt allocation without f2fs_lock_op() in expand_inode_data(). So, when we do fallocate() for a pinned file and trigger checkpoint very frequently and simultaneously. F2FS gets stuck in the below code of do_checkpoint() forever. f2fs_sync_meta_pages(sbi, META,

Re: [f2fs-dev] [PATCH] f2fs: protect new segment allocation in expand_inode_data

2020-05-27 Thread Chao Yu
On 2020/5/27 12:02, Daeho Jeong wrote: > From: Daeho Jeong > > Found a new segemnt allocation without f2fs_lock_op() in > expand_inode_data(). So, when we do fallocate() for a pinned file > and trigger checkpoint very frequently and simultaneously. F2FS gets > stuck in the below code of do_checkp

[PATCH] f2fs: protect new segment allocation in expand_inode_data

2020-05-26 Thread Daeho Jeong
From: Daeho Jeong Found a new segemnt allocation without f2fs_lock_op() in expand_inode_data(). So, when we do fallocate() for a pinned file and trigger checkpoint very frequently and simultaneously. F2FS gets stuck in the below code of do_checkpoint() forever. f2fs_sync_meta_pages(sbi, META,