RE: [f2fs-dev] [PATCH 2/3] f2fs: cover more area with nat_tree_lock

2016-01-05 Thread Chao Yu
> > Sent: Sunday, January 03, 2016 9:26 AM > > > To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org; > > > linux-f2fs-de...@lists.sourceforge.net > > > Cc: Jaegeuk Kim > > > Subject: [f2fs-dev] [PATCH 2/3] f2fs: cover more area with nat_tree_lock > > &g

Re: [f2fs-dev] [PATCH 2/3] f2fs: cover more area with nat_tree_lock

2016-01-05 Thread Jaegeuk Kim
.kernel.org; > > linux-f2fs-de...@lists.sourceforge.net > > Cc: Jaegeuk Kim > > Subject: [f2fs-dev] [PATCH 2/3] f2fs: cover more area with nat_tree_lock > > > > There was a subtle bug on nat cache management which incurs wrong nid > > allocation > > or wr

RE: [f2fs-dev] [PATCH 2/3] f2fs: cover more area with nat_tree_lock

2016-01-05 Thread Chao Yu
dev] [PATCH 2/3] f2fs: cover more area with nat_tree_lock > > There was a subtle bug on nat cache management which incurs wrong nid > allocation > or wrong block addresses when try_to_free_nats is triggered heavily. > This patch enlarges the previous coverage of nat_tree_lock to avoid

[PATCH 2/3] f2fs: cover more area with nat_tree_lock

2016-01-02 Thread Jaegeuk Kim
There was a subtle bug on nat cache management which incurs wrong nid allocation or wrong block addresses when try_to_free_nats is triggered heavily. This patch enlarges the previous coverage of nat_tree_lock to avoid data race. Signed-off-by: Jaegeuk Kim --- fs/f2fs/node.c | 29