From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] Some random fuzz test fixes
Date: Thu, 5 Jul 2018 15:37:27 +0800 [thread overview]
Message-ID: <20180705073731.18459-1-wqu@suse.com> (raw)
Can be fetched from github:
https://github.com/adam900710/btrfs-progs/tree/fuzzed_enhance
Some random bugs exposed by the ill-fated fuzz-test (003 never seems to
pass).
It will be a big work to make fuzz/003 to pass, but at least there are
some easy fixes.
Qu Wenruo (4):
btrfs-progs: check: Remove the ability to rebuild root overwritting
existing tree blocks
btrfs-progs: transaction: Error out other than panic when committing
transaction
btrfs-progs: check/original: Avoid infinite loop when failed to repair
inode
btrfs-progs: check/original: Don't overwrite return value when we
failed to repair
check/main.c | 46 +++++++++++++++++++++++++---------------------
transaction.c | 19 +++++++++++++------
2 files changed, 38 insertions(+), 27 deletions(-)
--
2.18.0
next reply other threads:[~2018-07-05 7:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 7:37 Qu Wenruo [this message]
2018-07-05 7:37 ` [PATCH 1/4] btrfs-progs: check: Remove the ability to rebuild root overwritting existing tree blocks Qu Wenruo
2018-07-05 8:50 ` Gu, Jinxiang
2018-07-05 9:41 ` Qu Wenruo
2018-07-06 1:53 ` Gu, Jinxiang
2018-08-02 19:36 ` David Sterba
2018-07-05 7:37 ` [PATCH 2/4] btrfs-progs: transaction: Error out other than panic when committing transaction Qu Wenruo
2018-07-05 9:33 ` Gu, Jinxiang
2018-07-05 7:37 ` [PATCH 3/4] btrfs-progs: check/original: Avoid infinite loop when failed to repair inode Qu Wenruo
2018-07-06 3:22 ` Gu, Jinxiang
2018-07-05 7:37 ` [PATCH 4/4] btrfs-progs: check/original: Don't overwrite return value when we failed to repair Qu Wenruo
2018-07-06 4:57 ` Gu, Jinxiang
2018-08-02 20:03 ` [PATCH 0/4] Some random fuzz test fixes 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=20180705073731.18459-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).