public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Andrew Morton <akpm@osdl.org>
Cc: reiser@namesys.com, reiserfs-list@namesys.com,
	linux-kernel@vger.kernel.org
Subject: Re: precise characterization of ext3 atomicity
Date: Thu, 4 Sep 2003 23:08:54 +0200	[thread overview]
Message-ID: <200309042308.54002.phillips@arcor.de> (raw)
In-Reply-To: <20030904131052.6ec6426d.akpm@osdl.org>

On Thursday 04 September 2003 22:10, Andrew Morton wrote:
> Daniel Phillips <phillips@arcor.de> wrote:
> > On Thursday 04 September 2003 17:55, Andrew Morton wrote:
> > > Hans Reiser <reiser@namesys.com> wrote:
> > > > Is it correct to say of ext3 that it guarantees and only guarantees
> > > > atomicity of writes that do not cross page boundaries?
> > >
> > > Yes.
> >
> > Is that just happenstance, or does Posix or similar mandate it?
>
> Happenstance.
>
> It's semi-trivial to do this in ext3.  You'd open the file with O_ATOMIC
> and a write() would either be completely atomic or would return -EFOO
> without having written anything.
>
> The thing which prevents this is the ranking order between journal_start()
> and lock_page().
>
> It's not trivial but also not too hard to change things so that
> journal_start() can rank outside lock_page() - this would also offer some
> CPU savings.
>
> Can't say that I'm terribly motivated about the feature though.

I'm relieved, I have always thought that some higher level synchronization is 
required for simultaneous writes.  So Hans might as well tell his fans that 
Ext3 makes no official guarantee, and neither does Linux.

Regards,

Daniel


  reply	other threads:[~2003-09-04 21:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-04 14:20 precise characterization of ext3 atomicity Hans Reiser
2003-09-04 15:55 ` Andrew Morton
2003-09-04 15:59   ` Hans Reiser
2003-09-04 16:12     ` Andrew Morton
2003-09-04 16:25       ` Hans Reiser
2003-09-04 18:15         ` Mike Fedyk
2003-09-04 16:05           ` Antonio Vargas
2003-09-04 18:37           ` Hans Reiser
2003-09-04 19:12             ` Mike Fedyk
2003-09-04 21:03               ` Hans Reiser
2003-09-04 19:28             ` Andreas Dilger
2003-09-04 21:32               ` Hans Reiser
2003-09-04 22:03                 ` Andreas Dilger
2003-09-05 13:47                   ` Chris Mason
2003-09-09 13:09                 ` Pavel Machek
2003-09-09 19:21                   ` Gábor Lénárt
2003-09-09 19:43                     ` Mike Fedyk
2003-09-04 20:16   ` Daniel Phillips
2003-09-04 20:10     ` Andrew Morton
2003-09-04 21:08       ` Daniel Phillips [this message]
2003-09-04 21:39         ` Hans Reiser
2003-09-04 21:59           ` Daniel Phillips

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=200309042308.54002.phillips@arcor.de \
    --to=phillips@arcor.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    /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