From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Felipe Monteiro de Carvalho <felipemonteiro.carvalho@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: Which features should I implement in my ext4 reader?
Date: Mon, 2 Sep 2013 20:07:18 +0800 [thread overview]
Message-ID: <20130902120718.GB1106@gmail.com> (raw)
In-Reply-To: <CACyNnZNhrmcpQRU+JcqSJeUYt3YNpyTyVArW_Jrp3e43owVf5Q@mail.gmail.com>
Hello,
Sorry for my late reply.
On Mon, Sep 02, 2013 at 11:40:15AM +0200, Felipe Monteiro de Carvalho wrote:
> Hello,
>
> Ok, I found the extra data over 60 bytes ... it is in an extended
> attribute called "data" in the space after the inode. The wiki says it
> should be called "system.data" =(
>
> Also the wiki says here
> https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Extended_Attributes
> that "Extended attributes, when >>>not<<<< stored after the inode,
> have a header ext4_xattr_ibody_header that is 4 bytes long:"
>
> Which in my oppinion is false, it should be: "Extended attributes,
> when stored after the inode, have a header ext4_xattr_ibody_header
> that is 4 bytes long:" without the "not"
>
> But I still am not sure of one thing: How can I know how many entries
> of extended attributes there are? Nothing in the wiki explains this =(
You need to traverse the all entries to get this value.
>
> Otherwise I cannot differentiate between yet another entry and simply
> data from an extended attribute...
You can use attribute name and name index to differentiate these
entries. You can read the comment at the front of fs/ext4/xattr.c and
it might help you to understand extended attribute.
Regards,
- Zheng
next prev parent reply other threads:[~2013-09-02 12:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 15:38 Which features should I implement in my ext4 reader? Felipe Monteiro de Carvalho
2013-08-14 5:06 ` Felipe Monteiro de Carvalho
2013-08-17 6:27 ` Felipe Monteiro de Carvalho
2013-08-17 13:02 ` Theodore Ts'o
2013-08-18 6:04 ` Felipe Monteiro de Carvalho
2013-08-19 5:08 ` Zheng Liu
2013-08-20 10:16 ` Felipe Monteiro de Carvalho
2013-08-20 10:39 ` Zheng Liu
2013-08-21 12:16 ` Felipe Monteiro de Carvalho
2013-08-23 12:54 ` Felipe Monteiro de Carvalho
2013-08-28 20:09 ` Felipe Monteiro de Carvalho
2013-09-02 9:40 ` Felipe Monteiro de Carvalho
2013-09-02 12:07 ` Zheng Liu [this message]
2013-09-02 12:35 ` Felipe Monteiro de Carvalho
2013-09-04 5:35 ` Zheng Liu
2013-09-05 5:25 ` jon ernst
[not found] ` <CAGW2f1FgHZsQbNMyWiD997UZz55y20qHJHryEcMsgpEwecxftA@mail.gmail.com>
2013-09-05 7:04 ` Felipe Monteiro de Carvalho
2013-09-05 7:41 ` Felipe Monteiro de Carvalho
2013-09-02 16:41 ` Darrick J. Wong
2013-08-19 14:03 ` Theodore Ts'o
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=20130902120718.GB1106@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=felipemonteiro.carvalho@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).