From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: <robert.munteanu@gmail.com>
Subject: [PATCH 0/3] Fix for infinite loop on non-empty inode but with no file extent
Date: Wed, 5 Aug 2015 16:03:11 +0800 [thread overview]
Message-ID: <1438761794-32738-1-git-send-email-quwenruo@cn.fujitsu.com> (raw)
A bug reported by Robert Munteanu, which btrfsck infinite loops on an
inode with discount file extent.
This patchset includes a fix in printing file extent hole, fix the
infinite loop, and corresponding test case.
BTW, thanks Robert Munteanu a lot for its detailed debug report, makes
it super fast to reproduce the error.
Qu Wenruo (3):
btrfs-progs: fsck: Print correct file hole
btrfs-progs: fsck: Fix a infinite loop on discount file extent repair
btrfs-progs: fsck-tests: Add test case for inode lost all its file
extent
cmds-check.c | 16 +++++++++++++++-
.../017-missing-all-file-extent/default_case.img.xz | Bin 0 -> 1104 bytes
2 files changed, 15 insertions(+), 1 deletion(-)
create mode 100644 tests/fsck-tests/017-missing-all-file-extent/default_case.img.xz
--
2.5.0
next reply other threads:[~2015-08-05 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 8:03 Qu Wenruo [this message]
2015-08-05 8:03 ` [PATCH 1/3] btrfs-progs: fsck: Print correct file hole Qu Wenruo
2015-08-05 8:03 ` [PATCH 2/3] btrfs-progs: fsck: Fix a infinite loop on discount file extent repair Qu Wenruo
2015-08-05 8:03 ` [PATCH 3/3] btrfs-progs: fsck-tests: Add test case for inode lost all its file extent Qu Wenruo
2015-08-05 16:40 ` [PATCH 0/3] Fix for infinite loop on non-empty inode but with no " David Sterba
2015-08-07 13:05 ` Robert Munteanu
2015-08-07 14:00 ` David Sterba
2015-08-07 14:17 ` Robert Munteanu
2015-08-07 14:19 ` David Sterba
2015-08-07 14:23 ` Robert Munteanu
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=1438761794-32738-1-git-send-email-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=robert.munteanu@gmail.com \
/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.