Re: [f2fs-dev] [PATCH 04/12] f2fs: remove wrong f2fs_bug_on when merging extents

2015-06-30 Thread Jaegeuk Kim
rnel.org; > > linux-f2fs-devel@lists.sourceforge.net > > Cc: Jaegeuk Kim > > Subject: [f2fs-dev] [PATCH 04/12] f2fs: remove wrong f2fs_bug_on when > > merging extents > > > > In f2fs_update_extent_tree, if there is existing extent, f2fs tries to split > > it w

Re: [f2fs-dev] [PATCH 04/12] f2fs: remove wrong f2fs_bug_on when merging extents

2015-06-29 Thread Chao Yu
v] [PATCH 04/12] f2fs: remove wrong f2fs_bug_on when merging > extents > > In f2fs_update_extent_tree, if there is existing extent, f2fs tries to split > it with two parts. > In each trial, __insert_extent_tree checks __is_front/back_mergeable, and then > if it hits to go, there

[f2fs-dev] [PATCH 04/12] f2fs: remove wrong f2fs_bug_on when merging extents

2015-06-29 Thread Jaegeuk Kim
In f2fs_update_extent_tree, if there is existing extent, f2fs tries to split it with two parts. In each trial, __insert_extent_tree checks __is_front/back_mergeable, and then if it hits to go, there is f2fs_bug_on(!den), which triggers a kernel panic. Actually, we don't need to check this. Instead