From: Felipe Monteiro de Carvalho <felipemonteiro.carvalho@gmail.com>
To: Felipe Monteiro de Carvalho <felipemonteiro.carvalho@gmail.com>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org
Subject: Re: Which features should I implement in my ext4 reader?
Date: Wed, 28 Aug 2013 22:09:42 +0200 [thread overview]
Message-ID: <CACyNnZOXOZ-uL+TO8HOuO4DoWsBKuBOX5RLQrZzyoeG1L2a9yg@mail.gmail.com> (raw)
In-Reply-To: <CACyNnZP2SFovG9YeBNeifm4KqrCzi7FU97CWVUjST0YQiqt3pQ@mail.gmail.com>
Hello,
Any idea where to find the extra data over 60 bytes in a very small
file (for example 120 bytes) would be greatly appreciated ... I
already tried the extra space after the inode but there was nothing
useful there! =/ Or at least nothing that matched the description of
the extended attributes. It should start with a magic number, but
started with many zeroes =/
thanks,
Felipe Monteiro de Carvalho
On Fri, Aug 23, 2013 at 2:54 PM, Felipe Monteiro de Carvalho
<felipemonteiro.carvalho@gmail.com> wrote:
> Hello,
>
> I went forward trying to implement this myself, but I am having trouble.
>
> Files up to 60 bytes work great, and large files too. But a file with
> 61 bytes does not.
>
> Reading ignoring the inline results in zero on all bytes, which can't
> be right, so I guess it is inlined.
>
> After the first 60 bytes I try to get the extended attribute, but
> i_file_acl_lo == FData.l_i_file_acl_high == 0
>
> And I think that it cannot possibly have the extended attribute data
> in block zero =/ (it contains DEADBEEF or something like that)
>
> Any ideas where I got this wrong or any tips about how to figure out
> in debugfs where the data is?
>
> thanks,
> --
> Felipe Monteiro de Carvalho
--
Felipe Monteiro de Carvalho
next prev parent reply other threads:[~2013-08-28 20:09 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 [this message]
2013-09-02 9:40 ` Felipe Monteiro de Carvalho
2013-09-02 12:07 ` Zheng Liu
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=CACyNnZOXOZ-uL+TO8HOuO4DoWsBKuBOX5RLQrZzyoeG1L2a9yg@mail.gmail.com \
--to=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).