From: "Ted Ts'o" <tytso@mit.edu>
To: Sam Gandhi <samgandhi9@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can someone explain s_xattr field in the superblock?
Date: Tue, 31 May 2011 19:28:15 -0400 [thread overview]
Message-ID: <20110531232815.GA4837@thunk.org> (raw)
In-Reply-To: <BANLkTikuz1c9dCB65PqrHCXMSt+7_cS11w@mail.gmail.com>
On Sat, May 28, 2011 at 08:52:41AM -0700, 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.
>
> 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 provides support for extended attributes, which is often
abbreviated as (not surpisingly) xattr. Some file systems don't
support extended attributes, so they don't need to setup s_xattr.
For more information, read the attr(5) man page: "man 5 attr".
- Ted
prev parent reply other threads:[~2011-06-01 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 15:52 Can someone explain s_xattr field in the superblock? Sam Gandhi
2011-05-31 23:28 ` Ted Ts'o [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=20110531232815.GA4837@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@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