Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Jan 2016 19:41:35 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-fs@FreeBSD.org
Subject:   [Bug 206059] [ext2fs][patch] EXT4: cannot mount filesystems < 512 MiB in size: "ext2fs: no space for extra inode timestamps"
Message-ID:  <bug-206059-3630-Y8IcVe0M7I@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206059-3630@https.bugs.freebsd.org/bugzilla/>
References:  <bug-206059-3630@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206059

Pedro F. Giffuni <pfg@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pfg@FreeBSD.org

--- Comment #1 from Pedro F. Giffuni <pfg@FreeBSD.org> ---
This is wrong:

Look at struct ext2fs_dinode (ext2_dinode.h). If the inode size is 128, the
extra timestamps really don't fit. Any attempt to read beyond the 128 would=
 be
a buffer overflow.

I recall the big block sizes were used for handling (non standard) extended
attributes and the extra_isize only started getting used with ext4.
I think this might be a bug in the GNU ext2fsprogs: technically you should
disable the extra_isize with tune2fs before mounting such filesystems.

--=20
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206059-3630-Y8IcVe0M7I>