On Mon, Jan 15, 2018 at 11:17:33AM +0200, Nikolay Borisov wrote: > On 5.12.2017 10:39, Nikolay Borisov wrote: > > Here is a series doing some minor code cleanups, hopefully making the code > > more idiomatic and easier to follow. They should be pretty low-risk and > > introduce no functional changes (patches 1-5). > > > > The the last 2 patches deal with a regression of btrfs rescue > > super-recovery. > > Turns out this was broken for sometime. Patch 6 introduces a regression test > > which hopefully will prevent further occurences and patch 7 fixes the > > actual > > bug. > > > > Nikolay Borisov (7): > > btrfs-progs: Explictly state test.sh must be executable > > btrfs-progs: Factor out common print_device_info > > btrfs-progs: Remove recover_get_good_super > > btrfs-progs: Use list_for_each_entry in write_dev_all_supers > > btrfs-progs: Document logic of btrfs_read_dev_super > > btrfs-progs: Add test for super block recovery > > btrfs-progs: Fix super-recovery > > > > chunk-recover.c | 18 ------- > > disk-io.c | 21 ++++++-- > > super-recover.c | 28 ++--------- > > tests/README.md | 4 +- > > tests/fsck-tests/029-superblock-recovery/test.sh | 64 > > ++++++++++++++++++++++++ > > utils.c | 18 +++++++ > > utils.h | 3 ++ > > 7 files changed, 110 insertions(+), 46 deletions(-) > > create mode 100755 tests/fsck-tests/029-superblock-recovery/test.sh > > > Gentle ping since I'd like to get this into next btrfs-progs version, > especially the "fix super-recovery" patch.
Series applied, thanks. I've swapped the order of test and fix as Qu pointed out and made some other minor fixups to the patches. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
