From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@kernel.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] xattr: Fix error results for non-existent / invisible attributes
Date: Mon, 20 Jun 2011 04:09:21 -0400 [thread overview]
Message-ID: <20110620080921.GA23159@infradead.org> (raw)
In-Reply-To: <201105271450.37089.agruen@kernel.org>
On Fri, May 27, 2011 at 02:50:36PM +0200, Andreas Gruenbacher wrote:
> Return -ENODATA when trying to read a user.* attribute which cannot
> exist: user space otherwise does not have a reasonable way to
> distinguish between non-existent and inaccessible attributes.
>
> Likewise, return -ENODATA when an unprivileged process tries to read a
> trusted.* attribute: to unprivileged processes, those attributes are
> invisible (listxattr() won't include them).
This breaks xfstests 062. It would also be very useful to send VFS
patches to linux-fsdevel, btw.
next prev parent reply other threads:[~2011-06-20 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 12:50 [PATCH] xattr: Fix error results for non-existent / invisible attributes Andreas Gruenbacher
2011-06-20 8:09 ` Christoph Hellwig [this message]
2011-06-21 1:34 ` Andreas Gruenbacher
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=20110620080921.GA23159@infradead.org \
--to=hch@infradead.org \
--cc=agruen@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox