From: davidsen@tmr.com (bill davidsen)
To: akpm@zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] sys_sync livelock fix
Date: Wed, 13 Feb 2002 09:09:57 -0500 [thread overview]
Message-ID: <200202131409.JAA10642@gatekeeper.tmr.com> (raw)
In-Reply-To: <3C69FB14.167B899E@zip.com.au>
In-Reply-To: <3C69EBB7.24EA9C05@zip.com.au> <Pine.LNX.3.96.1020213000859.8487A-100000@gatekeeper.tmr.com>
In article <3C69FB14.167B899E@zip.com.au> you write:
| Bill Davidsen wrote:
| >
| > > But we want sync to be useful.
| >
| > No one has proposed otherwise. Unless you think that a possible hang is
| > useful, the questions becomes adding all dirty buffers to the elevator,
| > then (a) waiting or (b) returning. Either satisfies SuSv2.
|
| errr. Bill. I wrote the patch. Please take this as a sign
| that I'm not happy with the current implementation :)
Sorry, I had been sitting at a keyboard for about 16 hours when I typed
that, and didn't look at the sender... Lot's of other typos in there as
well, sign of need for 3-4 hours sleep.
But I think sync(2) as a checkpoint, write out all dirty at the moment
of sync call, is fine and deterministic, and all that.
That serves the shutdown case as well, if there is a process in some
unkillable state, but somehow still writing, at least the system will go
down. I'm not sure any process not killable with kill -9 is able to do
anything, but I won't bet on it.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2002-02-13 14:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 23:13 [patch] sys_sync livelock fix 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 [this message]
2002-02-13 15:29 ` Daniel Phillips
2002-02-13 22:53 ` Bill Davidsen
2002-02-14 0:33 ` Daniel Phillips
2002-02-13 1:36 ` What is a livelock? (was: [patch] sys_sync livelock fix) Olaf Dietsche
2002-02-13 1:56 ` Andrew Morton
2002-02-13 2:30 ` Olaf Dietsche
2002-02-13 2:39 ` Andrew Morton
2002-02-13 16:19 ` Olaf Dietsche
2002-02-13 2:52 ` William Lee Irwin III
2002-02-18 22:19 ` David Schwartz
2002-02-13 2:33 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 9:18 [patch] sys_sync livelock fix Andries.Brouwer
2002-02-14 0:57 Andries.Brouwer
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=200202131409.JAA10642@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.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