From: Andrew Morton <akpm@linux-foundation•org>
To: David Miller <davem@davemloft•net>
Cc: ilpo.jarvinen@helsinki•fi, eric.dumazet@gmail•com,
shemminger@linux-foundation•org, netdev@vger•kernel.org,
kolo@albatani•cz, bugzilla-daemon@bugzilla•kernel.org
Subject: Re: [Bug 14470] New: freez in TCP stack
Date: Thu, 18 Mar 2010 14:04:24 -0700 [thread overview]
Message-ID: <20100318140424.aaf3ec24.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091202.222446.10943991.davem@davemloft.net>
On Wed, 02 Dec 2009 22:24:46 -0800 (PST)
David Miller <davem@davemloft•net> wrote:
> From: "Ilpo J__rvinen" <ilpo.jarvinen@helsinki•fi>
> Date: Thu, 26 Nov 2009 23:54:53 +0200 (EET)
>
> > [PATCH] tcp: clear hints to avoid a stale one (nfs only affected?)
>
> Ok, since Linus just released 2.6.32 I'm tossing this into net-next-2.6
> so it gets wider exposure.
>
> I still want to see test results from the bug reporter, and if it fixes
> things we can toss this into -stable too.
Despite my request to take this to email, quite a few people have been
jumping onto this report via bugzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=14470
Bit of a pita, but it'd be worth someone taking a look to ensure that
we're all talking about the same bug.
next prev parent reply other threads:[~2010-03-18 21:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 15:41 Fw: [Bug 14470] New: freez in TCP stack Stephen Hemminger
2009-10-28 22:13 ` Andrew Morton
2009-10-28 22:27 ` Denys Fedoryschenko
2009-10-29 5:35 ` Eric Dumazet
2009-10-29 5:59 ` Eric Dumazet
2009-10-29 6:02 ` David Miller
2009-10-29 8:00 ` David Miller
2009-11-26 21:54 ` Ilpo Järvinen
2009-11-26 23:37 ` David Miller
2009-11-27 6:17 ` Eric Dumazet
2009-12-02 23:10 ` David Miller
2009-12-03 6:24 ` David Miller
2010-03-18 21:04 ` Andrew Morton [this message]
2010-03-19 15:52 ` Ilpo Järvinen
2009-10-29 12:58 ` Fw: " Ilpo Järvinen
2009-10-29 14:08 ` Eric Dumazet
2009-10-30 20:18 ` Herbert Xu
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=20100318140424.aaf3ec24.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=bugzilla-daemon@bugzilla$(echo .)kernel.org \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=ilpo.jarvinen@helsinki$(echo .)fi \
--cc=kolo@albatani$(echo .)cz \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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