Re: [f2fs-dev] [PATCH 4/4] f2fs: avoid wrong f2fs_bug_on when truncating inline_data

2015-03-19 Thread Chao Yu
> > > Sent: Wednesday, March 18, 2015 12:58 AM > > > To: linux-ker...@vger.kernel.org; linux-fsde...@vger.kernel.org; > > > linux-f2fs-devel@lists.sourceforge.net > > > Cc: Jaegeuk Kim > > > Subject: [f2fs-dev] [PATCH 4/4] f2fs: avoid wrong f2fs_bug_

Re: [f2fs-dev] [PATCH 4/4] f2fs: avoid wrong f2fs_bug_on when truncating inline_data

2015-03-18 Thread Jaegeuk Kim
rnel.org; > > linux-f2fs-devel@lists.sourceforge.net > > Cc: Jaegeuk Kim > > Subject: [f2fs-dev] [PATCH 4/4] f2fs: avoid wrong f2fs_bug_on when > > truncating inline_data > > > > This patch removes wrong f2fs_bug_on in truncate_inline_inode. > > >

Re: [f2fs-dev] [PATCH 4/4] f2fs: avoid wrong f2fs_bug_on when truncating inline_data

2015-03-17 Thread Chao Yu
dev] [PATCH 4/4] f2fs: avoid wrong f2fs_bug_on when truncating > inline_data > > This patch removes wrong f2fs_bug_on in truncate_inline_inode. > > When there is no space, it can happen a corner case where i_isze is over > MAX_INLINE_SIZE while its inode is still inline_data.

[f2fs-dev] [PATCH 4/4] f2fs: avoid wrong f2fs_bug_on when truncating inline_data

2015-03-17 Thread Jaegeuk Kim
This patch removes wrong f2fs_bug_on in truncate_inline_inode. When there is no space, it can happen a corner case where i_isze is over MAX_INLINE_SIZE while its inode is still inline_data. The scenario is 1. write small data into file #A. 2. fill the whole partition to 100%. 3. truncate 4096