Re: [GIT PULL] overlayfs fix for 4.8-rc5

From: Miklos Szeredi
Date: Fri Sep 09 2016 - 17:18:34 EST

On Fri, Sep 9, 2016 at 10:36 PM, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> On Fri, Sep 9, 2016 at 1:08 PM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>> That code tries to remove ACL from a directory, and there are several cases:
>> 1) success: that's good obviously
>> 2) error: no ACL was found: that's also good
>> 3) error: ACL's are not supported by the filesystem: this is also good
>> 4) error: ACL was there but we failed to remove it for some other
>> reason: this is not good
>> The patch adds handling of case 3.
> I'm not convinced your explanation is correct.
> The thing is, you added a test for -EOPNOTSUPP, and that is in fact at
> least partly case (2) (eg xattr_resolve_name())
> And EOPNOTSUPP actually seems to be the _clear_ case. The ENODATA case
> is the one that is hard to actually verify. I tried to see that "yes,
> all filesystems return ENODATA", but it wasn't obvious at all (p9fs?)
> If I read the cifs code right, it returns EOPNOTSUPP for the "not
> found" case too.
> And ext2/ext4 returns ERANGE for some "we don't support that" cases,
> while gfs2 seems to return EINVAL for those cases. Those are obviously
> also cases of (2), but the fuse code doesn't test for it.
> So the error list seems to be rather random, and no, ENODATA and
> EOPNOTSUPP do not seem to be the only errors that would match the
> above at all.
> I dunno. I guess this is a corner case that really doesn't matter in
> practice, but the whole "let's test a few special cases" approach
> fails the smell test to me, and doesn't actually seem to match your
> cases above very well.

Okay, so how do we do this correctly? The desired end result is
clear: FOOBAR xattr doesn't exist on the directory. This "doesn't
exist" is a negative result, so the only way to check it is to check
for errors. Either with removexattr() or getxattr() this will get us
into the same trap: that there are multiple errors that have this

Same thing with ENOENT: checking for non-existence can be difficult,
because ENAMETOOLONG is actually a special form of ENOENT.

I just don't see the "right" soltion here, and while I agree that the
current one is ugly, it should actually work. We won't get ERANGE,
because the posix acl xattrs have short names that'll fit in all
filesystems and 9p isn't even a valid fs for the upper layer of an