From: Eryu Guan <guaneryu@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: Eryu Guan <guaneryu@gmail.com>, "Theodore Ts'o" <tytso@mit.edu>
Subject: [PATCH] ext4: don't cache out of order extents
Date: Thu, 17 Oct 2013 17:27:53 +0800 [thread overview]
Message-ID: <1382002073-27862-1-git-send-email-guaneryu@gmail.com> (raw)
A corrupted ext4 may have out of order leaf extents, i.e.
extent: lblk 0--1023, len 1024, pblk 9217, flags: LEAF UNINIT
extent: lblk 1000--2047, len 1024, pblk 10241, flags: LEAF UNINIT
^^^^ overlap with previous extent
Reading such extent could hit BUG_ON() in ext4_es_cache_extent().
BUG_ON(end < lblk);
The problem is that __read_extent_tree_block() tries to cache holes as
well but assumes 'lblk' is greater than 'prev' and passes underflowed
length to ext4_es_cache_extent().
I hit this when fuzz testing ext4, and am able to reproduce it by
modifying the on-disk extent by hand.
Ran xfstests on patched ext4 and no regression.
Cc: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
---
fs/ext4/extents.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 54d52af..c9ebcb9 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -503,7 +503,7 @@ __read_extent_tree_block(const char *function, unsigned int line,
ext4_lblk_t lblk = le32_to_cpu(ex->ee_block);
int len = ext4_ext_get_actual_len(ex);
- if (prev && (prev != lblk))
+ if (prev && (prev < lblk))
ext4_es_cache_extent(inode, prev,
lblk - prev, ~0,
EXTENT_STATUS_HOLE);
--
1.8.3.1
next reply other threads:[~2013-10-17 9:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 9:27 Eryu Guan [this message]
2013-10-17 13:44 ` [PATCH] ext4: don't cache out of order extents Lukáš Czerner
2013-10-17 14:40 ` Theodore Ts'o
2013-10-17 15:22 ` Lukáš Czerner
2013-10-17 15:58 ` Theodore Ts'o
2013-10-17 15:06 ` Eryu Guan
2013-10-20 13:27 ` [PATCH v2] ext4: check for overlapping extents in ext4_valid_extent_entries() Eryu Guan
2013-10-21 11:59 ` Eryu Guan
2013-10-21 12:47 ` Eryu Guan
2013-10-21 16:06 ` Lukáš Czerner
2013-10-22 18:40 ` Eryu Guan
2013-12-04 2:36 ` [PATCH v3] " Theodore Ts'o
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=1382002073-27862-1-git-send-email-guaneryu@gmail.com \
--to=guaneryu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).