From: David Woodhouse <dwmw2@infradead.org>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: Duplication of dirent names in JFFS2 summary
Date: Fri, 19 May 2006 16:33:11 +0100 [thread overview]
Message-ID: <1148052791.3875.180.camel@pmac.infradead.org> (raw)
In-Reply-To: <1148052379.3199.58.camel@sauron.oktetlabs.ru>
On Fri, 2006-05-19 at 19:26 +0400, Artem B. Bityutskiy wrote:
> 1. During scan nobody can access JFFS2, so "giving incorrect values to
> userspace until we've finished the scan" is wrong.
I shouldn't have said 'scan'. I should have said 'until the GC thread
has finished checking nodes'.
> 2. Before accessing *any* inode, read_inode() is called. So what I'm
> saying is to calculate *correct* nlink at the read_inode() time.
You can't do that. You don't have correct nlink until you've checked all
the dirents in _all_ the directories on the file system.
> I'm repeating for the 3rd time my statement: names (or their hashes) are
> only needed to calculate correct nlinks. We don't have to calculate
> correct nlinks at the *scan* time, we may try to do this at the
> *read_inode()* time. See what I mean?
I know what you mean, and it's _still_ not correct.
--
dwmw2
next prev parent reply other threads:[~2006-05-19 15:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 0:44 Duplication of dirent names in JFFS2 summary David Woodhouse
2006-05-19 1:01 ` David Woodhouse
2006-05-19 11:53 ` David Woodhouse
2006-05-19 11:58 ` Artem B. Bityutskiy
2006-05-19 12:11 ` David Woodhouse
2006-05-19 12:14 ` Artem B. Bityutskiy
2006-05-19 12:31 ` David Woodhouse
2006-05-19 14:34 ` Artem B. Bityutskiy
2006-05-19 14:59 ` David Woodhouse
2006-05-19 16:41 ` David Woodhouse
2006-05-19 16:43 ` David Woodhouse
2006-05-19 6:05 ` Jörn Engel
2006-05-19 10:08 ` David Woodhouse
2006-05-19 11:32 ` Artem B. Bityutskiy
2006-05-19 11:57 ` Artem B. Bityutskiy
2006-05-19 12:05 ` Artem B. Bityutskiy
2006-05-19 12:23 ` David Woodhouse
2006-05-19 14:17 ` Artem B. Bityutskiy
2006-05-19 14:50 ` David Woodhouse
2006-05-19 15:07 ` Artem B. Bityutskiy
2006-05-19 15:26 ` Artem B. Bityutskiy
2006-05-19 15:33 ` David Woodhouse [this message]
2006-05-19 15:38 ` Artem B. Bityutskiy
2006-05-19 15:43 ` David Woodhouse
2006-05-19 15:46 ` Artem B. Bityutskiy
2006-05-20 8:38 ` Artem B. Bityutskiy
2006-05-20 9:08 ` Artem B. Bityutskiy
2006-05-19 15:37 ` 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=1148052791.3875.180.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=dedekind@infradead.org \
--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