linux-ext4 - RHEL e2fsprogs-1.40.4-sb_feature_check

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CFEED6C0.B22C8%andreas.dilger@intel.com>
Date:	Fri, 18 Jul 2014 19:50:55 +0000
From:	"Dilger, Andreas" <andreas.dilger@...el.com>
To:	Eric Sandeen <sandeen@...hat.com>
CC:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: RHEL e2fsprogs-1.40.4-sb_feature_check_ignore.patch

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

Download attachment "e2fsprogs-1.40.4-sb_feature_check_ignore.patch" of type "application/octet-stream" (1196 bytes)