David Sterba 7b9586bc2b btrfs: tests: properly initialize fs_info of extent buffer ...

The fs_info is supposed to be valid, even though it's not used right
now and the test does not crash.

Signed-off-by: David Sterba <dsterba@suse.com>

2019-04-29 19:02:26 +02:00

..

btrfs-tests.c

btrfs: tests: add table of most common errors

2019-04-29 19:02:25 +02:00

btrfs-tests.h

btrfs: tests: add table of most common errors

2019-04-29 19:02:25 +02:00

extent-buffer-tests.c

btrfs: tests: use standard error message after path allocation failure

2019-04-29 19:02:26 +02:00

extent-io-tests.c

btrfs: tests: properly initialize fs_info of extent buffer

2019-04-29 19:02:26 +02:00

extent-map-tests.c

btrfs: tests: use standard error message after fs_info allocation failure

2019-04-29 19:02:25 +02:00

free-space-tests.c

btrfs: tests: use standard error message after block group allocation failure

2019-04-29 19:02:26 +02:00

free-space-tree-tests.c

btrfs: tests: use standard error message after block group allocation failure

2019-04-29 19:02:26 +02:00

inode-tests.c

btrfs: tests: use standard error message after inode allocation failure

2019-04-29 19:02:26 +02:00

qgroup-tests.c

btrfs: tests: use standard error message after path allocation failure

2019-04-29 19:02:26 +02:00