From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao2.yu@samsung.com>
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
Date: Tue, 28 Jul 2015 08:57:05 -0700 [thread overview]
Message-ID: <20150728155705.GA57016@jaegeuk-mac02.hsd1.ca.comcast.net> (raw)
In-Reply-To: <00e301d0c91f$d303dfc0$790b9f40$@samsung.com>
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 <jaegeuk@kernel.org>
> > ---
> > 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;
> > }
> >
> > ret = f2fs_sync_file(filp, 0, LLONG_MAX, 0);
> > @@ -1418,7 +1420,7 @@ static int f2fs_ioc_abort_volatile_write(struct file *filp)
> >
> > if (f2fs_is_atomic_file(inode)) {
> > clear_inode_flag(F2FS_I(inode), FI_ATOMIC_FILE);
> > - commit_inmem_pages(inode, false);
> > + commit_inmem_pages(inode, true);
> > }
> >
> > if (f2fs_is_volatile_file(inode))
> > diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> > index f7bfc3b..509a2c4 100644
> > --- a/fs/f2fs/segment.c
> > +++ b/fs/f2fs/segment.c
> > @@ -227,7 +227,7 @@ retry:
> > trace_f2fs_register_inmem_page(page, INMEM);
> > }
> >
> > -void commit_inmem_pages(struct inode *inode, bool abort)
> > +int commit_inmem_pages(struct inode *inode, bool abort)
> > {
> > struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> > struct f2fs_inode_info *fi = F2FS_I(inode);
> > @@ -239,6 +239,7 @@ void commit_inmem_pages(struct inode *inode, bool abort)
> > .rw = WRITE_SYNC | REQ_PRIO,
> > .encrypted_page = NULL,
> > };
> > + int err = 0;
> >
> > /*
> > * The abort is true only when f2fs_evict_inode is called.
> > @@ -263,8 +264,12 @@ void commit_inmem_pages(struct inode *inode, bool abort)
> > inode_dec_dirty_pages(inode);
> > trace_f2fs_commit_inmem_page(cur->page, INMEM);
> > fio.page = cur->page;
> > - do_write_data_page(&fio);
> > + err = do_write_data_page(&fio);
> > submit_bio = true;
> > + if (err) {
> > + unlock_page(cur->page);
>
> Shouldn't we invoke f2fs_put_page(,1) here?
This entry is not removed from the list.
So, after failure, the abort path will put the page and remove it from the list.
Thanks,
>
> > + break;
> > + }
> > }
> > f2fs_put_page(cur->page, 1);
> > } else {
> > @@ -283,6 +288,7 @@ void commit_inmem_pages(struct inode *inode, bool abort)
> > if (submit_bio)
> > f2fs_submit_merged_bio(sbi, DATA, WRITE);
> > }
> > + return err;
> > }
> >
> > /*
> > --
> > 2.1.1
> >
> >
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2015-07-28 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 0:21 [PATCH 1/2] f2fs: call set_page_dirty to attach i_wb for cgroup Jaegeuk Kim
2015-07-26 0:21 ` [PATCH 2/2] f2fs: handle error cases in commit_inmem_pages Jaegeuk Kim
2015-07-28 10:25 ` [f2fs-dev] " Chao Yu
2015-07-28 15:57 ` Jaegeuk Kim [this message]
2015-07-29 9:32 ` Chao Yu
2015-08-04 18:37 ` Jaegeuk Kim
2015-07-28 10:29 ` [f2fs-dev] [PATCH 1/2] f2fs: call set_page_dirty to attach i_wb for cgroup Chao Yu
2015-07-28 15:32 ` Jaegeuk Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150728155705.GA57016@jaegeuk-mac02.hsd1.ca.comcast.net \
--to=jaegeuk@kernel.org \
--cc=chao2.yu@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®