From: Eric Sandeen <sandeen@redhat.com>
To: "Dilger, Andreas" <andreas.dilger@intel.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: RHEL e2fsprogs-1.40.4-sb_feature_check_ignore.patch
Date: Fri, 18 Jul 2014 17:32:00 -0500 [thread overview]
Message-ID: <53C9A060.6090403@redhat.com> (raw)
In-Reply-To: <CFEED6C0.B22C8%andreas.dilger@intel.com>
On 7/18/14, 2:50 PM, Dilger, Andreas wrote:
> I was looking through the RHEL e2fsprogs.spec file and saw that you are
> still
> carrying the e2fsprogs-1.40.4-sb_feature_check_ignore.patch to avoid
> problems
> if the kernel sets xattrs on a new filesystem and doesn't copy this into
> the
> backup superblock.
Ugh, yeah, that's just been there forever, TBH, I forgot about it.
I'll actually have to refamiliarize myself with why it showed up years
ago! :)
> It seems that mke2fs enables the xattr feature in the superblock by default
> for all filesystems (courtesy of misc/default_profile.c), and e2fsck
> doesn't
> drop COMPAT_EXT_XATTR even if the filesystem doesn't have xattrs, so most
> of
> the danger of not having this patch are behind us.
>
> That said, it probably still makes sense to include this patch into the
> upstream e2fsprogs, unless there is some reason not to? It looks pretty
> low risk.
Well, ISTR at the time I added it, it was a hacky workaround, rather than
a proper fix. I'll have to look at it again.
-eric
> Cheers, Andreas
>
prev parent reply other threads:[~2014-07-18 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 19:50 RHEL e2fsprogs-1.40.4-sb_feature_check_ignore.patch Dilger, Andreas
2014-07-18 22:32 ` Eric Sandeen [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=53C9A060.6090403@redhat.com \
--to=sandeen@redhat.com \
--cc=andreas.dilger@intel.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).