tag 6d127367db5b2a55dcd9884601bf7de9ab957b0b
tagger Zorro Lang <zlang@kernel.org> Mon Dec 25 14:03:12 2023
object 17324dbc7743902aec349d12ccad91b3cb6005c5

Release fstests v2023.12.25

commit 17324dbc7743902aec349d12ccad91b3cb6005c5
author Naohiro Aota <naohiro.aota@wdc.com> Fri Dec 22 02:56:22 2023
committer Zorro Lang <zlang@kernel.org> Sat Dec 23 19:14:21 2023
tree 815680222e5988b9d3b2773967ca0d696e3338af
parent d6e9d32578afc1da2dd398cc46018f0a51d7875c

fstests: btrfs: use proper filter for subvolume deletion

Test cases btrfs/208, 233, 276 does not use _filter_btrfs_subvol_delete()
to process "btrfs subvolume delete" command's output. So, the following
diff occurs even with a previous fix.

btrfs/208       - output mismatch (see /host/btrfs/208.out.bad)
    --- tests/btrfs/208.out     2023-12-22 02:09:18.000000000 +0000
    +++ /host/btrfs/208.out.bad 2023-12-22 02:21:40.697036486 +0000
    @@ -6,12 +6,12 @@
     subvol1
     subvol2
     subvol3
    -Delete subvolume (no-commit): 'SCRATCH_MNT/subvol1'
    +Delete subvolume 256 (no-commit): 'SCRATCH_MNT/subvol1'
     After deleting one subvolume:
     subvol2
    ...

Let them use the filter and fix the output accordingly.

Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
Reviewed-by: David Disseldorp <ddiss@suse.de>
Signed-off-by: Zorro Lang <zlang@kernel.org>