From: David Woodhouse <dwmw2@infradead.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2_scan_eraseblock() - errors
Date: Wed, 31 Jul 2002 12:59:09 +0100 [thread overview]
Message-ID: <4164.1028116749@redhat.com> (raw)
In-Reply-To: <20020731115703.GB28984@wohnheim.fh-wedel.de>
joern@wohnheim.fh-wedel.de said:
> And this marking as obsolete is done how? Does is involve writes to
> the flash node, after it has already been written?
> Sorry for me being clueless.
Yep. There's a bit in the node type field which we clear to mark the node
obsolete. And I've been very strict about making sure it's an optimisation
_only_, and we never actually rely on being able do to it.
Deletion of directory entries, for example, could perhaps have been done
just by marking the original as obsolete, but instead we do it by writing a
new dirent with the same name and inode #0.
--
dwmw2
next prev parent reply other threads:[~2002-07-31 11:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 18:11 jffs2_scan_eraseblock() - errors Curtis, Allen
2002-07-30 22:21 ` David Woodhouse
2002-07-31 10:34 ` Jörn Engel
2002-07-31 11:45 ` David Woodhouse
2002-07-31 11:57 ` Jörn Engel
2002-07-31 11:59 ` David Woodhouse [this message]
2002-07-31 12:16 ` Jörn Engel
2002-07-31 12:17 ` David Woodhouse
2002-07-31 13:07 ` Jörn Engel
2002-07-31 21:12 ` Problems with full FS Joakim Tjernlund
2002-08-01 18:26 ` Oops when unlinking stale file Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 23:30 jffs2_scan_eraseblock() - errors Curtis, Allen
2002-07-30 23:42 ` David Woodhouse
2002-07-30 23:59 Curtis, Allen
2002-07-31 0:15 ` David Woodhouse
2002-07-31 0:18 ` David Woodhouse
2002-07-31 0:38 Curtis, Allen
2002-07-31 0:48 ` David Woodhouse
2002-07-31 1:15 Curtis, Allen
2002-07-31 3:07 ` David Woodhouse
2002-07-31 23:02 Curtis, Allen
2002-08-01 10:44 ` David Woodhouse
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=4164.1028116749@redhat.com \
--to=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--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