From: Chao Yu <chao2.yu@samsung.com>
To: "'Jaegeuk Kim'" <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH 1/2] f2fs: handle error cases in move_encrypted_block
Date: Wed, 15 Jul 2015 09:39:47 +0800 [thread overview]
Message-ID: <012501d0be9f$3ca52dc0$b5ef8940$@samsung.com> (raw)
In-Reply-To: <1436901502-78825-1-git-send-email-jaegeuk@kernel.org>
Hi Jaegeuk,
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Wednesday, July 15, 2015 3:18 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 1/2] f2fs: handle error cases in move_encrypted_block
>
> This patch fixes some missing error handlers.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/gc.c | 25 ++++++++++++++++---------
> 1 file changed, 16 insertions(+), 9 deletions(-)
>
> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> index 11046db..db11861 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -556,27 +556,34 @@ static void move_encrypted_block(struct inode *inode, block_t bidx)
> if (!fio.encrypted_page)
> goto put_out;
>
> - f2fs_submit_page_bio(&fio);
> -
> - /* allocate block address */
> - f2fs_wait_on_page_writeback(dn.node_page, NODE);
> -
> - allocate_data_block(fio.sbi, NULL, fio.blk_addr,
> - &fio.blk_addr, &sum, CURSEG_COLD_DATA);
> - dn.data_blkaddr = fio.blk_addr;
> + err = f2fs_submit_page_bio(&fio);
> + if (err)
> + goto put_page_out;
f2fs_submit_page_bio will put the page when failed.
So goto put_out is enough?
>
> /* write page */
> lock_page(fio.encrypted_page);
> +
> + if (unlikely(!PageUptodate(fio.encrypted_page)))
> + goto put_page_out;
> + if (unlikely(fio.encrypted_page->mapping != META_MAPPING(fio.sbi)))
> + goto put_page_out;
> +
> set_page_writeback(fio.encrypted_page);
> fio.rw = WRITE_SYNC;
> f2fs_submit_page_mbio(&fio);
>
> + /* allocate block address */
> + f2fs_wait_on_page_writeback(dn.node_page, NODE);
> + allocate_data_block(fio.sbi, NULL, fio.blk_addr,
> + &fio.blk_addr, &sum, CURSEG_COLD_DATA);
move above f2fs_submit_page_mbio(&fio) to here?
Thanks,
> + dn.data_blkaddr = fio.blk_addr;
> +
> set_data_blkaddr(&dn);
> f2fs_update_extent_cache(&dn);
> set_inode_flag(F2FS_I(inode), FI_APPEND_WRITE);
> if (page->index == 0)
> set_inode_flag(F2FS_I(inode), FI_FIRST_BLOCK_WRITTEN);
> -
> +put_page_out:
> f2fs_put_page(fio.encrypted_page, 1);
> put_out:
> f2fs_put_dnode(&dn);
> --
> 2.1.1
>
>
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud.
> GigeNET's Cloud Solutions provide you with the tools and support that
> you need to offload your IT needs and focus on growing your business.
> Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
> _______________________________________________
> 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-15 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 19:18 [PATCH 1/2] f2fs: handle error cases in move_encrypted_block Jaegeuk Kim
2015-07-14 19:18 ` [PATCH 2/2] f2fs: use a page temporarily for encrypted gced page Jaegeuk Kim
2015-07-15 1:43 ` [f2fs-dev] " Chao Yu
2015-07-15 1:39 ` Chao Yu [this message]
2015-07-15 22:42 ` [f2fs-dev] [PATCH 1/2] f2fs: handle error cases in move_encrypted_block 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='012501d0be9f$3ca52dc0$b5ef8940$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--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