From: Theodore Ts'o <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Bo Branten <bosse@acc.umu.se>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsck: zap extent-format inode with no extent header
Date: Mon, 30 Nov 2015 14:22:14 -0500 [thread overview]
Message-ID: <20151130192214.GF4316@thunk.org> (raw)
In-Reply-To: <20151128215132.GD10580@birch.djwong.org>
On Sat, Nov 28, 2015 at 01:51:32PM -0800, Darrick J. Wong wrote:
> The kernel requires all inodes with the extent flag set to have a
> valid extent tree header in i_block. The ext2fs_extent_open2 prefers
> to initialize the header if i_block is zeroed, but e2fsck never writes
> the new header to disk. Since the kernel won't create inodes with the
> flag and no header anyway, zap such files.
>
> Reported-by: Bo Branten <bosse@acc.umu.se>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Thanks, applied.
- Ted
prev parent reply other threads:[~2015-11-30 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 21:51 [PATCH] e2fsck: zap extent-format inode with no extent header Darrick J. Wong
2015-11-29 17:39 ` Bo Branten
2015-11-30 19:22 ` Theodore Ts'o [this message]
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=20151130192214.GF4316@thunk.org \
--to=tytso@mit.edu \
--cc=bosse@acc.umu.se \
--cc=darrick.wong@oracle.com \
--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).