linux-ext4 - Re: e2fsprogs: Richacl support

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-prev] [day] [month] [year] [list]

Message-ID: <20151019001704.GQ2678@thunk.org>
Date:	Sun, 18 Oct 2015 20:17:04 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Andreas Gruenbacher <agruenba@...hat.com>
Cc:	Dave Chinner <david@...morbit.com>,
	linux-ext4 <linux-ext4@...r.kernel.org>, xfs@....sgi.com
Subject: Re: e2fsprogs: Richacl support

On Mon, Oct 19, 2015 at 12:46:49AM +0200, Andreas Gruenbacher wrote:
> The filesystem sets the MS_POSIXACL super-block flag for POSIX ACLs or
> the MS_RICHACL super-block flag for richacls. These flags are checked
> with the IS_POSIXACL(inode) and IS_RICHACL(inode) macros.

Ah, OK.  So it's either one thing or another.

> I can send the validation code; not sure how removing corrupt xattrs
> would fit into e2fsck though. Can e2fsck remove individual xattrs?

Yep.  Using the libext2fs function ext2fs_xattr_remove(), in
lib/ext2fs/ext_attr.c.  This requires the development branch of
e2fsprogs, but by adding a new feature flag, richacl is going to
require a 1.43 version of e2fsprogs (not yet released, but hopefully
will be released soon).

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html