From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/6] btrfs-progs: Variant fixes for fuzz-tests
Date: Fri, 3 Aug 2018 13:50:16 +0800 [thread overview]
Message-ID: <20180803055022.9816-1-wqu@suse.com> (raw)
This can be fetched from github:
https://github.com/adam900710/btrfs-progs/tree/fixes_for_fuzz_test
The base HEAD is:
commit d7a1b84756157d544a9ddc399ef48c6132eaafcf (david/devel)
Author: Qu Wenruo <wqu@suse.com>
Date: Thu Jul 5 15:37:31 2018 +0800
btrfs-progs: check/original: Don't overwrite return value when we failed to repair
Thanks for the already merged fixes for fuzz/003, the remaining part is
pretty small now, +20/-7.
Mostly of the fixes are for fuzz/003, just a small bunch of BUG_ON()
removal. (Patch 1~3 and 5)
There is also a fix for fuzz/003 dead loop. (Patch 4)
Finally we have a fix for fuzz/007, the bug is a segfault triggered by
accessing poisoned list_head, caused by double list freeing. (Patch 6)
Now fuzz-test should finally work without problem.
Qu Wenruo (6):
btrfs-progs: Exit gracefully if we hit ENOSPC when allocating tree
block
btrfs-progs: Exit gracefully when failed to repair root dir item
btrfs-progs: Don't report dirty leaked eb using BUG_ON
btrfs-progs: Fix infinite loop when failed to repair bad key order
btrfs-progs: Exit gracefull when we failed to alloc dev extent
btrfs-progs: rescue-super: Don't double free fs_devices
check/main.c | 10 +++++++++-
extent-tree.c | 5 ++++-
extent_io.c | 6 +++++-
super-recover.c | 3 ---
volumes.c | 3 ++-
5 files changed, 20 insertions(+), 7 deletions(-)
--
2.18.0
next reply other threads:[~2018-08-03 7:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 5:50 Qu Wenruo [this message]
2018-08-03 5:50 ` [PATCH 1/6] btrfs-progs: Exit gracefully if we hit ENOSPC when allocating tree block Qu Wenruo
2018-08-29 14:30 ` Nikolay Borisov
2018-08-03 5:50 ` [PATCH 2/6] btrfs-progs: Exit gracefully when failed to repair root dir item Qu Wenruo
2018-08-29 14:31 ` Nikolay Borisov
2018-08-03 5:50 ` [PATCH 3/6] btrfs-progs: Don't report dirty leaked eb using BUG_ON Qu Wenruo
2018-08-29 14:52 ` Nikolay Borisov
2018-08-30 1:08 ` Qu Wenruo
2018-08-03 5:50 ` [PATCH 4/6] btrfs-progs: Fix infinite loop when failed to repair bad key order Qu Wenruo
2018-08-03 5:50 ` [PATCH 5/6] btrfs-progs: Exit gracefull when we failed to alloc dev extent Qu Wenruo
2018-08-29 14:59 ` Nikolay Borisov
2018-08-03 5:50 ` [PATCH 6/6] btrfs-progs: rescue-super: Don't double free fs_devices Qu Wenruo
2018-08-29 15:38 ` Nikolay Borisov
2018-08-30 1:16 ` Qu Wenruo
2018-08-29 5:27 ` [PATCH 0/6] btrfs-progs: Variant fixes for fuzz-tests Qu Wenruo
2018-09-11 16:38 ` David Sterba
2018-09-11 23:59 ` Qu Wenruo
2018-09-14 14:25 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180803055022.9816-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.