From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Dmitry Bazhenov <atrey@emcraft.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 node versioning problem?
Date: Wed, 03 May 2006 18:40:04 +0400 [thread overview]
Message-ID: <4458C0C4.9090601@yandex.ru> (raw)
In-Reply-To: <200605031828.51552.atrey@emcraft.com>
Dmitry Bazhenov wrote:
> I think it can happen. I can imagine at least one scenario where such
> situation can occur. Of course, in normal circumstances it is hardly possible
> but in the case of a powerfail it can be.
> 1. Assume, upon a call to jffs2_commit_write() function the
> f->highest_version has the maximum value.
> 2. jffs2_commit_write() increments f->highest_version which becomes 0.
> 3. jffs2_commit_write() invokes jffs2_write_dnode() with version=0.
I meant, whether it can happen with a real-life flash device taking into
account it's limited lifetime. Bear in mind, each eraseblock has limited
resource. I guess for huge flashes this may be the case, but JFFS2 is
not usable on them anyway. I'm too lazy to look at digits.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2006-05-03 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 11:56 JFFS2 node versioning problem? Dmitry Bazhenov
2006-05-03 12:02 ` Artem B. Bityutskiy
2006-05-03 14:28 ` Dmitry Bazhenov
2006-05-03 14:35 ` Dmitry Bazhenov
2006-05-03 14:42 ` Artem B. Bityutskiy
2006-05-03 14:40 ` Artem B. Bityutskiy [this message]
2006-05-03 15:07 ` Dmitry Bazhenov
2006-05-03 15:07 ` Josh Boyer
2006-05-03 15:11 ` Josh Boyer
2006-05-03 15:21 ` Jörn Engel
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=4458C0C4.9090601@yandex.ru \
--to=dedekind@yandex.ru \
--cc=atrey@emcraft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.