From: Eric Sandeen <sandeen@redhat.com>
To: Mingming Cao <cmm@us.ibm.com>
Cc: jvrao <jvrao@linux.vnet.ibm.com>, linux-ext4@vger.kernel.org
Subject: Re: lsetxattr/lgetxattr on ext4.
Date: Thu, 01 Apr 2010 17:01:11 -0500 [thread overview]
Message-ID: <4BB517A7.2060305@redhat.com> (raw)
In-Reply-To: <1270158896.2342.6.camel@mingming-laptop>
Mingming Cao wrote:
> On Wed, 2010-03-31 at 17:06 -0700, jvrao wrote:
>> lsetxattr()/lgetxsttr() functions are not working on a ext4 symlink.
>> But works fine on a regular file.
>>
>> I tried the following program.. Not sure if I am missing something.
>> Any help will be appreciated.
>>
>>
>
>
> I tried your test program on ext2/3/btrfs, it seems all broken.
> Not sure how this not being visible? Thought xattrs are heavily used by
> default on some distros.
xfs as well FWIW.
however, I'm not sure setting user xattrs directly on symlinks is
a common operation...
-Eric
next prev parent reply other threads:[~2010-04-01 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 0:06 lsetxattr/lgetxattr on ext4 jvrao
2010-04-01 21:54 ` Mingming Cao
2010-04-01 22:01 ` Eric Sandeen [this message]
2010-04-01 22:34 ` jvrao
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=4BB517A7.2060305@redhat.com \
--to=sandeen@redhat.com \
--cc=cmm@us.ibm.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
/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).