From: Andries.Brouwer@cwi.nl
To: davidsen@tmr.com, jgarzik@mandrakesoft.com
Cc: akpm@zip.com.au, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org, viro@math.psu.edu
Subject: Re: [patch] sys_sync livelock fix
Date: Wed, 13 Feb 2002 09:18:39 GMT [thread overview]
Message-ID: <UTC200202130918.JAA3212400.aeb@cwi.nl> (raw)
> Yow, your message inspired me to re-read SuSv2 and indeed confirm,
As a side note, these days you should be reading SuSv3,
it is an official standard now. See, for example,
http://www.UNIX-systems.org/version3/
http://www.opengroup.org/onlinepubs/007904975/toc.htm
> sync(2) schedules I/O but can return before completion
Don't forget that this standard does not describe what is
desirable, but describes the minimum guaranteed by all
Unices considered.
Having a sync that returns without having written the data
is not especially useful. Also without the sync this data
would have been written sooner or later.
We changed sync to wait, long ago, because otherwise shutdown
would cause filesystem corruption.
Andries
next reply other threads:[~2002-02-13 9:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 9:18 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-14 0:57 Andries.Brouwer
2002-02-12 23:13 Andrew Morton
2002-02-12 23:31 ` Alan Cox
2002-02-12 23:22 ` Andrew Morton
2002-02-13 0:28 ` Alan Cox
2002-02-13 3:28 ` Bill Davidsen
2002-02-13 3:46 ` Jeff Garzik
2002-02-13 15:11 ` Daniel Phillips
2002-02-13 22:24 ` Bill Davidsen
2002-02-13 22:41 ` Mike Fedyk
2002-02-14 0:26 ` Daniel Phillips
2002-02-14 0:37 ` Andrew Morton
2002-02-14 0:49 ` Daniel Phillips
2002-02-14 0:53 ` Andrew Morton
2002-02-14 1:27 ` Daniel Phillips
2002-02-14 1:29 ` Andrew Morton
2002-02-14 1:59 ` Mike Fedyk
2002-02-14 2:07 ` Daniel Phillips
2002-02-13 23:31 ` Rob Landley
2002-02-14 0:44 ` Daniel Phillips
2002-02-12 23:29 ` Rik van Riel
2002-02-13 0:25 ` Alan Cox
2002-02-13 0:15 ` Rik van Riel
2002-02-13 0:36 ` Alan Cox
2002-02-13 0:36 ` Rik van Riel
2002-02-13 0:39 ` Andrew Morton
2002-02-13 3:42 ` Bill Davidsen
2002-02-13 3:54 ` Bill Davidsen
2002-02-13 4:01 ` Jeff Garzik
2002-02-13 4:53 ` Bill Davidsen
2002-02-13 15:17 ` Daniel Phillips
2002-02-13 4:29 ` Andrew Morton
2002-02-13 5:21 ` Bill Davidsen
2002-02-13 5:35 ` Andrew Morton
2002-02-18 2:29 ` Bill Davidsen
2002-02-13 14:09 ` bill davidsen
2002-02-13 15:29 ` Daniel Phillips
2002-02-13 22:53 ` Bill Davidsen
2002-02-14 0:33 ` 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=UTC200202130918.JAA3212400.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®