linux-ext4 - Re: Richacl and ext4 vs. xfs

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: <D3B85625-6E65-42A4-9935-17D5C9D65414@dilger.ca>
Date:   Fri, 4 Nov 2016 16:48:05 -0600
From:   Andreas Dilger <adilger@...ger.ca>
To:     Steve French <smfrench@...il.com>
Cc:     samba-technical <samba-technical@...ts.samba.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Andreas Gruenbacher <agruenba@...hat.com>,
        Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: Richacl and ext4 vs. xfs

[added linux-ext4 to CC list]

On Nov 4, 2016, at 1:19 PM, Steve French <smfrench@...il.com> wrote:
> 
> Andreas,
> I had been working on getting some VMs together to experiment with a
> few different Richacl configurations and it looks like the e2fsprogs
> git hub repo with richacl enhanced ext4 utilities may need to be
> updated or have an incompatibility with current kernels (See e2fsprogs
> github link at http://www.bestbits.at/richacl/ ).  XFS worked ok.
> 
> Fedora 24 Workstation, created two extra disks
> /dev/sdb for xfs
> /dev/sdc for ext4
> 
> Built and installed Andreas's 4.9.0-rc1 based kernel richacl branch
> and the other repos (xfsprogs, richacl etc.).    Had no problem
> formatting and using /dev/sdb1 as xfs, but once I installed e2fsprogs
> from Andreas's tree I couldn't boot the system (removed e2fsprogs and
> the ext4 partition and booted fine).  With Andreas's e2fsprogs I
> couldn't boot 4.9.0-rc1

What version of e2fsprogs is (the other) Andreas' tree based on?  The
newer e2fsprogs-1.43 has support for metadata checksums, but this should
be off by default in the released version.  The testing version had it
enabled by default.

With the working e2fsprogs, you could run:

 dumpe2fs -h /dev/sdb1 | grep -i feature

and see what features are enabled (in particular metadata_csum, and maybe
if the RichACL has its own feature flag)?

Cheers, Andreas






Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)