From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12534] New: ext4 extent structure backwards
Date: Sat, 24 Jan 2009 01:31:39 -0800 (PST) [thread overview]
Message-ID: <bug-12534-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=12534
Summary: ext4 extent structure backwards
Product: File System
Version: 2.5
KernelVersion: 2.6.28
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: markus@cs.wisc.edu
Latest working kernel version: 2.6.28
Earliest failing kernel version: 2.6.28
Distribution: Gentoo
Hardware Environment: i686
I was figuring out ext4 with hexedit (don't ask), and I noticed that the extent
structure is backwards. It's defined in ext4_extents.h with this order:
block(32-bit), len(16), start_hi(16), start_lo(32)
Here's what I see (including 12 byte header):
0A F3 01 00 04 00 00 00 00 00 00 00
00 00 00 00 01 00 00 00 3E 17 13 00
(another 36 bytes of zeros)
You can see that the block is 0x13173e, len is 1, and start is 0. (The
header's just fine, and only says that there is 1 extent and there can be no
more than 4 extents.)
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-01-24 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 9:31 bugme-daemon [this message]
2009-01-24 16:07 ` [Bug 12534] ext4 extent structure backwards bugme-daemon
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=bug-12534-13602@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).