From: Andi Kleen <ak@muc.de>
To: James Morris <jmorris@intercode.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Martin Pool <mbp@samba.org>,
"David S. Miller" <davem@redhat.com>,
kuznet@ms2.inr.ac.ru, ak@muc.de, netdev@oss.sgi.com,
Alan.Cox@linux.org
Subject: Re: FIN_WAIT1 / TCP_CORK / 2.2 -- reproducible bug and test case
Date: Thu, 3 Oct 2002 05:54:46 +0200 [thread overview]
Message-ID: <20021003035446.GA29860@averell> (raw)
In-Reply-To: <Mutt.LNX.4.44.0210031329450.13240-100000@blackbird.intercode.com.au>
On Thu, Oct 03, 2002 at 05:30:44AM +0200, James Morris wrote:
> On 30 Sep 2002, Alan Cox wrote:
>
> > Well if Dave can't test it and isnt doing any 2.2 who wants to be the
> > 2.2 networking maintainer ?
> >
>
> I'd be willing to give it a go.
2.2 networking unfortunately has some more SMP bugs (DaveM can tell you details)
which are hard to fix. So think twice before you volunteer ;)
-Andi
next prev parent reply other threads:[~2002-10-03 3:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 2:03 FIN_WAIT1 / TCP_CORK / 2.2 -- reproducible bug and test case Martin Pool
2002-09-18 1:58 ` David S. Miller
2002-09-18 2:09 ` Martin Pool
2002-09-18 23:38 ` Alexey Kuznetsov
2002-09-26 5:47 ` Martin Pool
2002-09-26 13:09 ` kuznet
2002-09-26 20:46 ` David S. Miller
2002-09-30 9:59 ` Martin Pool
2002-09-30 10:32 ` David S. Miller
2002-09-30 12:23 ` Alan Cox
2002-10-03 3:30 ` James Morris
2002-10-03 3:54 ` Andi Kleen [this message]
2002-10-03 7:59 ` David S. Miller
2002-10-03 7:56 ` David S. Miller
2002-09-18 2:30 ` Martin Pool
-- strict thread matches above, loose matches on Subject: below --
2002-10-04 15:06 James Morris
2002-10-04 23:27 ` Martin Pool
2002-10-05 7:51 ` Martin Pool
2002-10-05 11:53 ` James Morris
2002-10-08 10:21 ` Martin Pool
2002-10-08 10:28 ` James Morris
2002-10-10 16:36 ` James Morris
2002-10-10 16:43 ` James Morris
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=20021003035446.GA29860@averell \
--to=ak@muc.de \
--cc=Alan.Cox@linux.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mbp@samba.org \
--cc=netdev@oss.sgi.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 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.