From owner-freebsd-fs@freebsd.org  Mon Jan 11 19:41:35 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09042A6B2CC
 for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 11 Jan 2016 19:41:35 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E61AF1333
 for <freebsd-fs@FreeBSD.org>; Mon, 11 Jan 2016 19:41:34 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u0BJfYCV082874
 for <freebsd-fs@FreeBSD.org>; Mon, 11 Jan 2016 19:41:34 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
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"
Date: Mon, 11 Jan 2016 19:41:35 +0000
X-Bugzilla-Reason: AssignedTo CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: pfg@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
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/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2016 19:41:35 -0000

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.=