From: Theodore Ts'o <tytso@mit.edu>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: e2fsprogs: Richacl support
Date: Sun, 18 Oct 2015 20:17:04 -0400 [thread overview]
Message-ID: <20151019001704.GQ2678@thunk.org> (raw)
In-Reply-To: <CAHc6FU7J9OESpAJzOKOmu-UP-bC_kzKT-oVg-MVKAaVzswOacA@mail.gmail.com>
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-10-19 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 16:03 e2fsprogs: Richacl support Andreas Gruenbacher
2015-10-16 23:16 ` Theodore Ts'o
2015-10-17 0:22 ` Andreas Gruenbacher
2015-10-17 14:39 ` Theodore Ts'o
2015-10-17 22:59 ` Dave Chinner
2015-10-18 0:35 ` Theodore Ts'o
2015-10-18 20:46 ` Andreas Gruenbacher
2015-10-18 21:44 ` Theodore Ts'o
2015-10-18 22:46 ` Andreas Gruenbacher
2015-10-19 0:17 ` Theodore Ts'o [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=20151019001704.GQ2678@thunk.org \
--to=tytso@mit.edu \
--cc=agruenba@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.