From: Jan Kara <jack@suse.cz>
To: Sam Gandhi <samgandhi9@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Can someone explain s_xattr field in the superblock?
Date: Tue, 31 May 2011 20:47:03 +0200 [thread overview]
Message-ID: <20110531184703.GA20905@quack.suse.cz> (raw)
In-Reply-To: <BANLkTikRjT6Ey-ZdMgXnoUaiO8wt0WACQw@mail.gmail.com>
Hello,
On Tue 31-05-11 11:23:33, Sam Gandhi wrote:
> I have seen some file systems like jffs2/ext4 etc setup the s_xattr
> field in the superblock structure.
> But there are files systems that do not initialize s_xattr field in
> the superblock.
Only filesystems that support extended attributes setup s_xattr.
> Can someone kindly explain what functionality does s_xattr on super
> block provides? What kinds of things file system wouldn't be able to
> do if the superblock doesn't have this initialized?
It tells VFS what callbacks to call when user tries to obtain/change
extended attributes. If s_xattr is left at NULL, user will get EOPNOTSUPP
or similar error...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2011-05-31 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 18:23 Can someone explain s_xattr field in the superblock? Sam Gandhi
2011-05-31 18:47 ` Jan Kara [this message]
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=20110531184703.GA20905@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=samgandhi9@gmail.com \
/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).