From: David Woodhouse <dwmw2@infradead.org>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org, Bruce_Leonard@selinc.com
Subject: Re: For UBIFS users: be aware of write-back!
Date: Fri, 03 Oct 2008 08:57:56 +0100 [thread overview]
Message-ID: <1223020676.3328.28.camel@macbook.infradead.org> (raw)
In-Reply-To: <1223019946.8051.45.camel@sauron>
On Fri, 2008-10-03 at 10:45 +0300, Artem Bityutskiy wrote:
> "In contrast, JFFS2 does not have write-back support and all the JFFS2
> file system changes go the flash synchronously. Well, this is not
> completely true and JFFS2 does have a small buffer of a NAND page
> size, but it is small and we may treat JFFS2 as completely
> synchronous."
That's quite poorly phrased. You may _not_ treat JFFS2 as completely
synchronous. You treat it like a normal file system, or it's going to
eat your babies.
There was a reason I was perfectly happy to make the change which made
JFFS2 start requiring fsync() like normal file systems -- it was because
people should have been doing it _anyway_.
Anyone who was skipping the required sync handling because they 'knew'
that it didn't matter on JFFS2, even though it didn't cost them anything
anyway -- and who didn't wake up at 3am every morning in a cold sweat,
worrying that it might have broken today -- deserves to be taken out
back and shot.
When it comes to correctness, people shouldn't have to do anything
special for different file systems. If there is _anything_ fs-specific
about the correctness issues, you are doing something WRONG (cf. NFS).
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-10-03 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 5:51 For UBIFS users: be aware of write-back! Artem Bityutskiy
2008-10-03 7:15 ` David Woodhouse
2008-10-03 7:45 ` Artem Bityutskiy
2008-10-03 7:57 ` David Woodhouse [this message]
2008-10-03 8:03 ` Artem Bityutskiy
2008-10-03 8:11 ` Artem Bityutskiy
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=1223020676.3328.28.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=Bruce_Leonard@selinc.com \
--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