linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: RHEL e2fsprogs-1.40.4-sb_feature_check_ignore.patch
Date: Fri, 18 Jul 2014 19:50:55 +0000	[thread overview]
Message-ID: <CFEED6C0.B22C8%andreas.dilger@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

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.

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.

Cheers, Andreas
-- 
Andreas Dilger

Lustre Software Architect
Intel High Performance Data Division



[-- Attachment #2: e2fsprogs-1.40.4-sb_feature_check_ignore.patch --]
[-- Type: application/octet-stream, Size: 1196 bytes --]

Index: e2fsprogs-1.41.5/e2fsck/super.c
===================================================================
--- e2fsprogs-1.41.5.orig/e2fsck/super.c
+++ e2fsprogs-1.41.5/e2fsck/super.c
@@ -869,7 +869,11 @@ void check_super_block(e2fsck_t ctx)
  * unfortunately, we shouldn't ignore it since if it's not set in the
  * backup, the extended attributes in the filesystem will be stripped
  * away.
+ *
+ * Well, I'm still going that route for now, 'til I do something
+ * better.  Full-fsck after a fresh install is just no good.  -ERS
  */
+#define FEATURE_COMPAT_IGNORE		(EXT2_FEATURE_COMPAT_EXT_ATTR)
 #define FEATURE_RO_COMPAT_IGNORE	(EXT2_FEATURE_RO_COMPAT_LARGE_FILE| \
 					 EXT4_FEATURE_RO_COMPAT_DIR_NLINK)
 #define FEATURE_INCOMPAT_IGNORE
(EXT3_FEATURE_INCOMPAT_EXTENTS| \
@@ -921,6 +925,9 @@ int check_backup_super_block(e2fsck_t ct
 			(EXT2_INODE_SIZE(backup_sb) < EXT2_GOOD_OLD_INODE_SIZE))
 			continue;
 
+#define SUPER_COMPAT_DIFFERENT(x)      \
+	((fs->super->x & ~FEATURE_COMPAT_IGNORE) !=     \
+	 (backup_sb->x & ~FEATURE_COMPAT_IGNORE))
 #define SUPER_INCOMPAT_DIFFERENT(x)    \
 	((fs->super->x & ~FEATURE_INCOMPAT_IGNORE) !=   \
 	 (backup_sb->x & ~FEATURE_INCOMPAT_IGNORE))

             reply	other threads:[~2014-07-18 19:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 19:50 Dilger, Andreas [this message]
2014-07-18 22:32 ` RHEL e2fsprogs-1.40.4-sb_feature_check_ignore.patch Eric Sandeen

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=CFEED6C0.B22C8%andreas.dilger@intel.com \
    --to=andreas.dilger@intel.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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).