From: "Dave Young" <hidave.darkstar@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: 2.6.24-rc8-mm1 : net tcp_input.c warnings
Date: Wed, 23 Jan 2008 15:44:54 +0800 [thread overview]
Message-ID: <a8e1da0801222344l101c2b90s363821c26bc8cb55@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801230937270.31652@kivilampi-30.cs.helsinki.fi>
On Jan 23, 2008 3:41 PM, Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> wrote:
>
> On Tue, 22 Jan 2008, David Miller wrote:
>
> > From: "Dave Young" <hidave.darkstar@gmail.com>
> > Date: Wed, 23 Jan 2008 09:44:30 +0800
> >
> > > On Jan 22, 2008 6:47 PM, Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> wrote:
> > > > [PATCH] [TCP]: debug S+L
> > >
> > > Thanks, If there's new findings I will let you know.
> >
> > Thanks for helping with this bug Dave.
>
> I noticed btw that there thing might (is likely to) spuriously trigger at
> WARN_ON(sacked != tp->sacked_out); because those won't be equal when SACK
> is not enabled. If that does happen too often, I send a fixed patch for
> it, yet, the fact that I print print tp->rx_opt.sack_ok allows
> identification of those cases already as it's zero when SACK is not
> enabled.
>
> Just ask if you need the updated debug patch.
Thanks, please send, I would like to get it.
>
> --
> i.
next prev parent reply other threads:[~2008-01-23 7:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 7:55 Dave Young
2008-01-21 21:14 ` Ilpo Järvinen
2008-01-22 4:37 ` Dave Young
2008-01-22 9:09 ` Dave Young
2008-01-22 9:18 ` Dave Young
2008-01-22 10:47 ` Ilpo Järvinen
2008-01-23 1:44 ` Dave Young
2008-01-23 3:01 ` David Miller
2008-01-23 7:41 ` Ilpo Järvinen
2008-01-23 7:44 ` Dave Young [this message]
2008-01-23 8:41 ` Ilpo Järvinen
2008-01-23 11:01 ` Ilpo Järvinen
2008-01-24 2:42 ` Dave Young
2008-01-24 9:54 ` Ilpo Järvinen
2008-01-24 10:24 ` Ilpo Järvinen
2008-01-24 10:46 ` Krishna Kumar2
2008-01-24 13:11 ` Kamalesh Babulal
2008-01-25 1:30 ` Dave Young
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=a8e1da0801222344l101c2b90s363821c26bc8cb55@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®