From: "Jörn Engel" <joern@lazybastard.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: R&D4 <r&d4@dave-tech.it>,
mtd_mailinglist <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 as transactional FS (in other words: how to be sure that data have been writtent correctly from userspace)
Date: Thu, 8 Mar 2007 14:12:58 +0100 [thread overview]
Message-ID: <20070308131257.GD23216@lazybastard.org> (raw)
In-Reply-To: <1173359044.3461.433.camel@pmac.infradead.org>
On Thu, 8 March 2007 13:04:04 +0000, David Woodhouse wrote:
> On Thu, 2007-03-08 at 13:54 +0100, Jörn Engel wrote:
> >
> > Last time I checked, JFFS2 got one case wrong. Don't remember which
> > one,
> > but there are not that many to check:
> > - mount -o sync
> > - open(..., O_SYNC);
>
> I don't think we've implemented those two at all.
Then you have your bug report. Ignoring those was ok in 2001, but with
wbuf I would at least expect JFFS2 to return an error.
One option for implementing this would be to do the write, call schedule
to let other processes write something, then check whether the buffer
has been flushed out by other processes. Or do some GC to fill the
buffer with useful data. Anything but padding it.
Jörn
--
The strong give up and move away, while the weak give up and stay.
-- unknown
next prev parent reply other threads:[~2007-03-08 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 9:49 JFFS2 as transactional FS (in other words: how to be sure that data have been writtent correctly from userspace) R&D4
2007-03-08 10:51 ` David Woodhouse
2007-03-08 12:54 ` Jörn Engel
2007-03-08 13:04 ` David Woodhouse
2007-03-08 13:12 ` Jörn Engel [this message]
2007-03-08 13:22 ` David Woodhouse
2007-03-08 13:44 ` Josh Boyer
2007-03-08 13:58 ` David Woodhouse
2007-03-08 14:35 ` Josh Boyer
2007-03-08 14:43 ` 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=20070308131257.GD23216@lazybastard.org \
--to=joern@lazybastard.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=r&d4@dave-tech.it \
/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