[PATCH 0/5] btrfs decoding fixes

[Dmitry V. Levin]

On Thu, May 26, 2016 at 11:33:02PM -0400, jeffm at suse.com wrote:
> 
> After submitting the last patch, I hunted down the last of the test case
> failures.  These are all failures in the output side of a RW ioctl and
> those test cases weren't easily runnable.  They are now, provided
> a btrfs file system is made available to them via a BTRFS_MOUNTPOINT
> environment variable during testing.
> 
> Three of the print_array conversions introduced bugs.  The search tree
> buffer isn't an array at all -- it's a series of variable length
> records, each with a header.  The btrfs_data_container element count
> refers to the number of 64-bit items rather than the number of
> 3*64-bit-sized records.
> 
> There was a stray "..." instead of printing the search buffer output
> in the BTRFS_IOC_TREE_SEARCH case and some broken whitespace in the _V2
> case.
> 
> -Jeff
> 
> ---
> Jeff Mahoney (5):
>   btrfs.c: fix print_array usage in btrfs_print_logical_ino_container
>   btrfs.c: don't use print_array in btrfs_print_tree_search
>   tests/btrfs.c: fix live btrfs_test_search_ioctls output
>   tests: check decoding of btrfs RDWR ioctls returned data

I've merged these, thanks.

>   file_ioctl.c: fix FIDEDUPERANGE output

Waiting for your comment whether this is really needed.


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20160527/e91676a2/attachment.bin>