From: Liu Bo <bo.li.liu@oracle.com>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix leak of subvolume writers counter
Date: Mon, 30 Jan 2017 12:21:00 -0800 [thread overview]
Message-ID: <20170130202100.GB10490@localhost.localdomain> (raw)
In-Reply-To: <1485583614-26225-1-git-send-email-fdmanana@kernel.org>
On Sat, Jan 28, 2017 at 06:06:54AM +0000, fdmanana@kernel.org wrote:
> From: Robbie Ko <robbieko@synology.com>
>
> When falling back from a nocow write to a regular cow write, we were
> leaking the subvolume writers counter in 2 situations, preventing
> snapshot creation from ever completing in the future, as it waits
> for that counter to go down to zero before the snapshot creation
> starts.
>
> In run_delalloc_nocow, maybe not release subv_writers conter,
> will lead to create snapshot hang.
Reviewed-by: Liu Bo <bo.li.liu@oracle.com>
Thanks,
-liubo
>
> Signed-off-by: Robbie Ko <robbieko@synology.com>
> Reviewed-by: Filipe Manana <fdmanana@suse.com>
> [Improved changelog and subject]
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
> fs/btrfs/inode.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> index a713d9d..7221d66 100644
> --- a/fs/btrfs/inode.c
> +++ b/fs/btrfs/inode.c
> @@ -1404,10 +1404,16 @@ static noinline int run_delalloc_nocow(struct inode *inode,
> * either valid or do not exist.
> */
> if (csum_exist_in_range(fs_info, disk_bytenr,
> - num_bytes))
> + num_bytes)) {
> + if (!nolock)
> + btrfs_end_write_no_snapshoting(root);
> goto out_check;
> - if (!btrfs_inc_nocow_writers(fs_info, disk_bytenr))
> + }
> + if (!btrfs_inc_nocow_writers(fs_info, disk_bytenr)) {
> + if (!nolock)
> + btrfs_end_write_no_snapshoting(root);
> goto out_check;
> + }
> nocow = 1;
> } else if (extent_type == BTRFS_FILE_EXTENT_INLINE) {
> extent_end = found_key.offset +
> --
> 2.7.0.rc3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-01-30 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 6:06 [PATCH] Btrfs: fix leak of subvolume writers counter fdmanana
2017-01-30 20:21 ` Liu Bo [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=20170130202100.GB10490@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).