public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2/xattr problems.
Date: Mon, 12 Jun 2006 10:53:15 +0100	[thread overview]
Message-ID: <1150105995.8184.17.camel@pmac.infradead.org> (raw)
In-Reply-To: <448D3752.3090605@ak.jp.nec.com>

On Mon, 2006-06-12 at 18:43 +0900, KaiGai Kohei wrote:
> In my opinion, a xattr across multiple nodes isn't neccesary.
> What do you think?

I'd be happier if it worked -- some of us have plans to abuse XATTR
support by building a simple database on it... :)

But as long as the failure mode is _graceful_, I suppose we can live
without it for now, if ext3 is also limited to 4KiB.

I'm looking through your handling of deletion now... I'm not sure that
we _need_ the physical deletion node for xdata, do we? Those can go away
just because there are no xrefs which link to them, just like our inodes
do?

Also, the physical deletion node for xrefs is only needed when the xattr
is deleted _without_ the inode being deleted. When the inode goes away,
again the xref becomes obsolete all by itself, right?

Finally, we need to be careful about garbage collection of deletion
nodes. Remember that the deletion node might be garbage-collected
_before_ the older node which it is deleting. So you must decide whether
to write the deletion node out again, when you are garbage collecting
it.

See the horrid mess we make of 'deletion dirents'.

-- 
dwmw2

  reply	other threads:[~2006-06-12  9:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20 18:41 JFFS2/xattr problems David Woodhouse
2006-05-21  3:22 ` David Woodhouse
2006-05-21 11:24   ` KaiGai Kohei
2006-05-21 11:19 ` KaiGai Kohei
2006-05-21 12:41   ` David Woodhouse
2006-06-12  2:17   ` KaiGai Kohei
2006-06-12  8:03     ` David Woodhouse
2006-06-12  9:43       ` KaiGai Kohei
2006-06-12  9:53         ` David Woodhouse [this message]
2006-06-12 18:06           ` Jörn Engel
2006-06-13 13:36             ` KaiGai Kohei
2006-06-13 14:13               ` Jörn Engel
2006-06-14 21:58                 ` Theodore Tso
2006-06-15 11:47                   ` Jörn Engel
2006-06-15 15:24                     ` Theodore Tso
2006-06-13 13:30           ` KaiGai Kohei
2006-06-24  5:58             ` KaiGai Kohei
2006-06-24 12:44               ` David Woodhouse
2006-06-26 15:45               ` David Woodhouse
2006-06-27  2:43                 ` KaiGai Kohei
2006-06-29  6:02                   ` KaiGai Kohei

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=1150105995.8184.17.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=kaigai@ak.jp.nec.com \
    --cc=linux-mtd@lists.infradead.org \
    /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