All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.20pre2aa1
Date: Wed, 16 May 2001 16:04:12 +0200	[thread overview]
Message-ID: <20010516160412.B15796@athlon.random> (raw)
In-Reply-To: <20010515235859.A2415@athlon.random> <Pine.LNX.4.33.0105152029580.7281-100000@twinlark.arctic.org>
In-Reply-To: <Pine.LNX.4.33.0105152029580.7281-100000@twinlark.arctic.org>; from dean-list-linux-kernel@arctic.org on Tue, May 15, 2001 at 08:33:05PM -0700

On Tue, May 15, 2001 at 08:33:05PM -0700, dean gaudet wrote:
> On Tue, 15 May 2001, Andrea Arcangeli wrote:
> 
> > o	fixed race in wake-one LIFO in accept(2). Apache must be compiled with
> > 	-DSINGLE_LISTEN_UNSERIALIZED_ACCEPT to take advantage of that.
> >
> > 00_wake-one-4
> >
> > 	Backport 2.4 waitqueues and in turn fixes an hanging condition in accept(2).
> >
> > 	(me)
> 
> apache since 1.3.15 has defined SINGLE_LISTEN_UNSERIALIZED_ACCEPT ...

That's definitely a good thing.

> 'cause that's what you guys asked me to do :)  does this mean there are
> known hangs on linux 2.2.x without your fix?

I never heard of anybody reproducing that but accpet() in 2.2
can _definitely_ miss events without the above 00_wake-one-4 patch
because it wrongly considers a progress wakeing up two times the same
exclusive task.

Furthmore the exclusive wakeup logic with the exclusive information
per-task and not per wait_queue_t will screwup if the tasks registers
itself like a wakeall after it was just registered as wakeone somewhere
else (however this second thing is more a theorical issue that shouldn't
trigger in 2.2).

Andrea

  reply	other threads:[~2001-05-16 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-15 21:58 2.2.20pre2aa1 Andrea Arcangeli
2001-05-16  3:33 ` 2.2.20pre2aa1 dean gaudet
2001-05-16 14:04   ` Andrea Arcangeli [this message]
2001-05-16 17:25     ` 2.2.20pre2aa1 dean gaudet
2001-05-16 17:40       ` 2.2.20pre2aa1 Andrea Arcangeli
2001-05-16 23:46       ` 2.2.20pre2aa1 Alan Cox

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=20010516160412.B15796@athlon.random \
    --to=andrea@suse.de \
    --cc=dean-list-linux-kernel@arctic.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.