linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 20 Aug 2013 18:39:56 +0800	[thread overview]
Message-ID: <20130820103956.GA7846@gmail.com> (raw)
In-Reply-To: <CACyNnZN4z_mHq86+FPOaGpzjwBVmmsKNjnd45s53o2LdQjxEsg@mail.gmail.com>

On Tue, Aug 20, 2013 at 12:16:09PM +0200, Felipe Monteiro de Carvalho wrote:
> On Mon, Aug 19, 2013 at 7:08 AM, Zheng Liu <gnehzuil.liu@gmail.com> wrote:
> > You need to checkout to e2fsprogs/pu branch.  All patches for inline data
> > are on this branch.  BTW, the latest refinement of patches had been sent
> > to the mailing list [1].  It would be great if you could give it a try.
> >
> > 1. http://comments.gmane.org/gmane.comp.file-systems.ext4/39825
> 
> Ok I can try this branch, but I wonder if other tools will work too. I
> need also to be able to add some files and directories to the
> partition.

I add some new interfaces in libext2fs to manipulate a file system
with inline data feature.  You can use libext2fs to add some files and
directories.  But these interfaces might be changed because it isn't
exported as an ABI.  After it is released within a new e2fsprogs
version, they will never be changed.

> 
> Will "mount" from a linux with kernel 3.8 work with a partition
> generated with this new e2fsprogs?

Yes, you can mount a file system with inline data in a 3.8 kernel using
this branch.

Regards,
                                                - Zheng

  reply	other threads:[~2013-08-20 10:39 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 [this message]
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
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=20130820103956.GA7846@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).