Re: [PATCH] Btrfs: handle pending renames with recycled inodes properly

[Josef Bacik <jbacik@fb.com>]

On 08/24/2016 05:07 AM, Filipe Manana wrote:
> On Tue, Aug 23, 2016 at 6:22 PM, Josef Bacik <jbacik@fb.com> wrote:
>> Suppose you have the following tree in snap1 on a file system mounted with -o
>> inode_cache so that inode numbers are recycled
>>
>> └── [    258]  a
>>     └── [    257]  b
>>
>> and then you remove b, rename a to c, and then re-create b in c so you have the
>> following tree
>>
>> └── [    258]  c
>>     └── [    257]  b
>>
>> and then you try to do an incremental send you will hit
>>
>> ASSERT(pending_move == 0);
>
> Hi Josef,
>
> Would you care submitting a regression test for xfstests?
> The change looks good to me.
>

Yeah I sent one yesterday, btrfs/131.  Thanks,

Josef