From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Jaakko Hyv?tti <jaakko@hyvatti.iki.fi>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc2-mm2
Date: Fri, 8 Oct 2004 04:24:55 -0700 [thread overview]
Message-ID: <20041008112455.GH9106@holomorphy.com> (raw)
In-Reply-To: <20041002004938.175203ba.akpm@osdl.org>
Jaakko Hyv?tti <jaakko@hyvatti.iki.fi> wrote:
>> Forgive me for asking a question that probably enough research would
>> answer, but which exact patch of those listed does fix this problem? I
>> cannot find the right one myself, and I would like to just address this
>> problem that has haunted me at least since 2.6.6, I guess. Or is the fix
>> too interdependent with other changes?
On Sat, Oct 02, 2004 at 12:49:38AM -0700, Andrew Morton wrote:
> It was wait_on_bit-must-loop.patch.
> But that simply fixes a bug which was introduced into an earlier
> 2.6.9-rcX-mmY kernel. The bug is certainly not present in any Linus
> kernel, nor in any 2.6.6/7/8 kernel.
> So you're seeing something different. Please send a full report.
Well, for the record, it's that otherwise one would have to honor the
invariant of no spurious wakeups, which e.g. jbd does not. There
actually was API forethought put into timeouts, but jbd uses a timer
and wake_up_process() instead of schedule_timeout(), and is nontrivial
to convert. It was also anticipated that e.g. other users may trip up.
-- wli
next prev parent reply other threads:[~2004-10-08 11:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 20:12 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 20:48 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 20:54 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 21:05 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 20:55 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-22 20:59 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 21:04 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-22 21:10 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-22 21:02 ` 2.6.9-rc2-mm2 Stefan Seyfried
2004-09-22 22:27 ` 2.6.9-rc2-mm2 Peter Williams
2004-09-23 1:47 ` 2.6.9-rc2-mm2 Nuno Ferreira
2004-09-23 2:03 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-23 2:58 ` 2.6.9-rc2-mm2 Herbert Xu
2004-09-23 9:29 ` 2.6.9-rc2-mm2 Nuno Ferreira
2004-09-23 3:00 ` 2.6.9-rc2-mm2 Nick Piggin
2004-09-23 5:07 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 5:27 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 5:46 ` 2.6.9-rc2-mm2 Peter Williams
2004-09-23 6:01 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 13:15 ` 2.6.9-rc2-mm2 Vladimir Saveliev
2004-09-23 15:51 ` 2.6.9-rc2-mm2 (disable repacker) Mike Houston
2004-09-23 16:48 ` 2.6.9-rc2-mm2 William Lee Irwin III
2004-09-23 17:59 ` 2.6.9-rc2-mm2 Akinobu Mita
2004-09-24 0:53 ` 2.6.9-rc2-mm2 [u] Martin Schlemmer [c]
2004-10-02 7:44 ` 2.6.9-rc2-mm2 Jaakko Hyvätti
2004-10-02 7:49 ` 2.6.9-rc2-mm2 Andrew Morton
2004-10-02 18:21 ` 2.6.9-rc2-mm2 Jaakko Hyvätti
2004-10-08 11:24 ` William Lee Irwin III [this message]
[not found] <747804697@toto.iv>
2004-09-23 0:39 ` 2.6.9-rc2-mm2 Peter Chubb
2004-09-23 0:43 ` 2.6.9-rc2-mm2 Jesse Barnes
2004-09-23 6:23 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-23 0:49 ` 2.6.9-rc2-mm2 Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-09-23 16:10 2.6.9-rc2-mm2 Luck, Tony
2004-09-23 18:31 ` 2.6.9-rc2-mm2 Andrew Morton
2004-09-24 6:27 2.6.9-rc2-mm2 Tim Krieglstein
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=20041008112455.GH9106@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=jaakko@hyvatti.iki.fi \
--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