From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Jason Hrycay <jhrycay@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, C.Fries@motorola.com,
jason.hrycay@motorola.com
Subject: Re: [PATCH] f2fs: move f2fs_balance_fs from truncate to punch_hole
Date: Tue, 09 Apr 2013 17:55:02 +0900 [thread overview]
Message-ID: <1365497702.4353.67.camel@kjgkr> (raw)
In-Reply-To: <51636BFC.6040607@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2111 bytes --]
Hi,
2013-04-08 (월), 20:16 -0500, Jason Hrycay:
> From: Jason Hrycay <jason.hrycay@motorola.com>
>
> Move the f2fs_balance_fs out of the truncate_hole function and only
> perform that in punch_hole use case. The commit:
>
> ed60b1644e7f7e5dd67d21caf7e4425dff05dad0
>
> intended to do this but moved it into truncate_hole to cover more
> cases. However, a deadlock scenario is possible when deleting an inode
> entry under specific conditions:
>
> f2fs_delete_entry()
> mutex_lock_op(sbi, DENTRY_OPS);
> truncate_hole()
> f2fs_balance_fs()
> mutex_lock(&sbi->gc_mutex);
> f2fs_gc()
> write_checkpoint()
> block_operations()
> mutex_lock_op(sbi, DENTRY_OPS);
>
> Lets move it into the punch_hole case to cover the original intent of
> avoiding it during fallocate's expand_inode_data case.
Agreed.
Thanks,
>
> Change-Id: I29f8ea1056b0b88b70ba8652d901b6e8431bb27e
> Signed-off-by: Jason Hrycay <jason.hrycay@motorola.com>
> ---
> fs/f2fs/file.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index e031f57..155b362 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -390,8 +390,6 @@ int truncate_hole(struct inode *inode, pgoff_t pg_start, pgoff_t pg_end)
> struct dnode_of_data dn;
> struct f2fs_sb_info *sbi = F2FS_SB(inode->i_sb);
>
> - f2fs_balance_fs(sbi);
> -
> mutex_lock_op(sbi, DATA_TRUNC);
> set_new_dnode(&dn, inode, NULL, NULL, 0);
> err = get_dnode_of_data(&dn, index, LOOKUP_NODE);
> @@ -435,6 +433,9 @@ static int punch_hole(struct inode *inode, loff_t offset, loff_t len, int mode)
> if (pg_start < pg_end) {
> struct address_space *mapping = inode->i_mapping;
> loff_t blk_start, blk_end;
> + struct f2fs_sb_info *sbi = F2FS_SB(inode->i_sb);
> +
> + f2fs_balance_fs(sbi);
>
> blk_start = pg_start << PAGE_CACHE_SHIFT;
> blk_end = pg_end << PAGE_CACHE_SHIFT;
> -- 1.8.0
--
Jaegeuk Kim
Samsung
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-04-09 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 1:16 Jason Hrycay
2013-04-09 6:46 ` Namjae Jeon
2013-04-09 8:56 ` Jaegeuk Kim
2013-04-09 8:55 ` Jaegeuk Kim [this message]
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=1365497702.4353.67.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=C.Fries@motorola.com \
--cc=jason.hrycay@motorola.com \
--cc=jhrycay@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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®