Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753974AbbHDShn (ORCPT ); Tue, 4 Aug 2015 14:37:43 -0400 Received: from mail.kernel.org ([198.145.29.136]:56891 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753681AbbHDShk (ORCPT ); Tue, 4 Aug 2015 14:37:40 -0400 Date: Tue, 4 Aug 2015 11:37:53 -0700 From: Jaegeuk Kim To: Chao Yu Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: handle error cases in commit_inmem_pages Message-ID: <20150804183753.GB69437@jaegeuk-mac02.hsd1.ca.comcast.net> References: <1437870077-46892-1-git-send-email-jaegeuk@kernel.org> <1437870077-46892-2-git-send-email-jaegeuk@kernel.org> <00e301d0c91f$d303dfc0$790b9f40$@samsung.com> <20150728155705.GA57016@jaegeuk-mac02.hsd1.ca.comcast.net> <011a01d0c9e1$8ead48d0$ac07da70$@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <011a01d0c9e1$8ead48d0$ac07da70$@samsung.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2947 Lines: 79 On Wed, Jul 29, 2015 at 05:32:00PM +0800, Chao Yu wrote: > Hi Jaegeuk, > > > -----Original Message----- > > From: Jaegeuk Kim [mailto:jaegeuk@kernel.org] > > Sent: Tuesday, July 28, 2015 11:57 PM > > To: Chao Yu > > Cc: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org; > > linux-f2fs-devel@lists.sourceforge.net > > Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: handle error cases in commit_inmem_pages > > > > On Tue, Jul 28, 2015 at 06:25:26PM +0800, Chao Yu wrote: > > > Hi Jaegeuk, > > > > > > > -----Original Message----- > > > > From: Jaegeuk Kim [mailto:jaegeuk@kernel.org] > > > > Sent: Sunday, July 26, 2015 8:21 AM > > > > To: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org; > > > > linux-f2fs-devel@lists.sourceforge.net > > > > Cc: Jaegeuk Kim > > > > Subject: [f2fs-dev] [PATCH 2/2] f2fs: handle error cases in commit_inmem_pages > > > > > > > > This patch adds to handle error cases in commit_inmem_pages. > > > > If an error occurs, it stops to write the pages and return the error right > > > > away. > > > > > > > > Signed-off-by: Jaegeuk Kim > > > > --- > > > > fs/f2fs/f2fs.h | 2 +- > > > > fs/f2fs/file.c | 6 ++++-- > > > > fs/f2fs/segment.c | 10 ++++++++-- > > > > 3 files changed, 13 insertions(+), 5 deletions(-) > > > > > > > > diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h > > > > index e73f2e2..58b05b5 100644 > > > > --- a/fs/f2fs/f2fs.h > > > > +++ b/fs/f2fs/f2fs.h > > > > @@ -1697,7 +1697,7 @@ void destroy_node_manager_caches(void); > > > > * segment.c > > > > */ > > > > void register_inmem_page(struct inode *, struct page *); > > > > -void commit_inmem_pages(struct inode *, bool); > > > > +int commit_inmem_pages(struct inode *, bool); > > > > void f2fs_balance_fs(struct f2fs_sb_info *); > > > > void f2fs_balance_fs_bg(struct f2fs_sb_info *); > > > > int f2fs_issue_flush(struct f2fs_sb_info *); > > > > diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c > > > > index 25d1a2f..a2b3656 100644 > > > > --- a/fs/f2fs/file.c > > > > +++ b/fs/f2fs/file.c > > > > @@ -1358,7 +1358,9 @@ static int f2fs_ioc_commit_atomic_write(struct file *filp) > > > > > > > > if (f2fs_is_atomic_file(inode)) { > > > > clear_inode_flag(F2FS_I(inode), FI_ATOMIC_FILE); > > > > - commit_inmem_pages(inode, false); > > > > + ret = commit_inmem_pages(inode, false); > > > > + if (ret) > > > > + return ret; > > It looks we forget to call mnt_drop_write_file before return. Oh, yes. :) I fixed that. Thanks, > > [snip] > > > This entry is not removed from the list. > > So, after failure, the abort path will put the page and remove it from the list. > > Oh, you're right, thanks for your explanation! :) > > Thanks, -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/