From: "J. Bruce Fields" <bfields@fieldses.org>
To: DENIEL Philippe <philippe.deniel@cea.fr>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: v9fs (9p): syscall setxattr inside kernel 3.14-rc1 returns size of set xattr
Date: Tue, 18 Feb 2014 13:04:50 -0500 [thread overview]
Message-ID: <20140218180450.GG4319@fieldses.org> (raw)
In-Reply-To: <5303666F.7000706@cea.fr>
On Tue, Feb 18, 2014 at 02:55:59PM +0100, DENIEL Philippe wrote:
> I run v9fs as a client on a F20, in front of my Ganesha server (see
> http://github.com/nfs-ganesha for details), using 9p.2000L
> My acl non-regression test showed errors when I installed a recent
> 3.14-rc1 kernel (I got it from kernel.org) on my F20 box.
> Investigation showed that the setfacl command line got messy because
> setxattr() (called from acl_set_modify() in libattr.so) return a
> non-zero value when successful. Further investigation showed that
> this behavior seems to come from v9fs_fid_xattr_set() inside
> fs/9p/xattr.c in the kernel's source.
>
> It seems like setxattr syscall does now return the size of the set
> xattr, and that seems to be the root cause of my problem. I do not
> believe that this change in setxattr is no bug, but a new feature.
> So I guess I should patch my libattr and/or glibc to use xattr/acl
> with kernel 3.14-rc1.
> Question is : where could I get the right version of libattr source
> treee (eventually with libacl if needed).
New kernel features shouldn't break old libraries--sounds like a bug.
--b.
next prev parent reply other threads:[~2014-02-18 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 13:55 v9fs (9p): syscall setxattr inside kernel 3.14-rc1 returns size of set xattr DENIEL Philippe
2014-02-18 18:04 ` J. Bruce Fields [this message]
[not found] ` <5304BAC2.3050508@cea.fr>
[not found] ` <CAFkjPT=mSR5RLrMEOtzPrmiE558hOLNoTH0SL4D7tho4azOpmQ@mail.gmail.com>
[not found] ` <CAGG-pUSEsThPiE+3sm75GVoE7QwuEhwRnT+0+2=osFdKLbQMOA@mail.gmail.com>
2014-08-21 11:10 ` Fwd: " Geyslan Gregório Bem
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=20140218180450.GG4319@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=philippe.deniel@cea.fr \
/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;
as well as URLs for NNTP newsgroup(s).