Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/4] Btrfs: fix wrong send_in_progress accounting
Date: Tue, 07 Jan 2014 09:27:11 +0800	[thread overview]
Message-ID: <52CB57EF.1060606@cn.fujitsu.com> (raw)
In-Reply-To: <20140106163015.GX6498@twin.jikos.cz>

On 01/07/2014 12:30 AM, David Sterba wrote:
> On Mon, Jan 06, 2014 at 05:25:06PM +0800, Wang Shilong wrote:
>> Steps to reproduce:
>>
>>   # mkfs.btrfs -f /dev/sda8
>>   # mount /dev/sda8 /mnt
>>   # btrfs sub snapshot -r /mnt /mnt/snap1
>>   # btrfs sub snapshot -r /mnt /mnt/snap2
>>   # btrfs send /mnt/snap2 -p /mnt/snap1
>>
>> As @send_root will also add into clone_sources, and we should
>> take care not to decrease its count twice.
> Yes, send_root is appended to the clone_roots but the
> clone_sources_to_rollback does not track this, it's not updated after
> it's added in
>
>    sctx->clone_roots[sctx->clone_roots_cnt++].root = sctx->send_root;
>
> so send->root->send_in_progress is not modified in the loop that
> decrements all clone_root's counters again.
>
> I don't see the warning that should catch negative values of the counter
> in btrfs_root_dec_send_in_progress. Am I missing something?
just run 'dmesg' after the above commands.

Thanks,
Wang
>
>
> david
> --
> 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
>


  reply	other threads:[~2014-01-07  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06  9:25 [PATCH 1/4] Btrfs: fix wrong send_in_progress accounting Wang Shilong
2014-01-06 16:30 ` David Sterba
2014-01-07  1:27   ` Wang Shilong [this message]
2014-01-07  3:10   ` Wang Shilong
2014-01-07  3:12     ` Wang Shilong

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=52CB57EF.1060606@cn.fujitsu.com \
    --to=wangsl.fnst@cn.fujitsu.com \
    --cc=dsterba@suse.cz \
    --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