From: Will Dyson <will_dyson@pobox.com>
To: linux-fsdevel@vger.kernel.org
Subject: i_op->listxattr semantics
Date: Sat, 07 Jun 2003 21:34:34 -0400 [thread overview]
Message-ID: <1055036074.27963.367.camel@thalience> (raw)
Hello all,
I am attempting to implement support for extended attributes in the Be
Filesystem (befs) driver. But I am stuck trying to figure out why the
getfattr program does not list my attributes.
Below is a test version of befs_listxattr that gives all files one
attribute named "MyAttr". When I mount my filesystem on /befs (in
2.5.69-uml) and issue the command "getfattr -d /befs", no attributes are
printed. The debugging statements appear in my syslog, so I know the
function is being called.
Can anyone help me figure out what I am doing wrong? Thanks!
static ssize_t
befs_listxattr(struct dentry *dentry, char *buffer, size_t size)
{
struct super_block *sb = dentry->d_inode->i_sb;
ssize_t attr_len = 0;
char *attr = "MyAttr";
befs_debug(sb, "---> befs_listxattr for inode %lu "
"with %d buffer_size",
dentry->d_inode->i_ino, size);
attr_len = strlen(attr);
if (buffer) {
memcpy(buffer, attr, attr_len);
buffer[attr_len] = '\0';
}
befs_debug(sb, "<--- befs_listxattr");
return attr_len + 1;
}
--
Will Dyson
"Back off man, I'm a scientist!" -Dr. Peter Venkman
next reply other threads:[~2003-06-08 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 1:34 Will Dyson [this message]
2003-06-08 2:07 ` i_op->listxattr semantics Nathan Scott
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=1055036074.27963.367.camel@thalience \
--to=will_dyson@pobox.com \
--cc=linux-fsdevel@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 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.