From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Neal Cardwell <ncardwell@google.com>
Cc: Christian Kujau <lists@nerdbynature.de>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: at net/ipv4/tcp_input.c:3418
Date: Tue, 6 Mar 2012 09:07:27 +0100 [thread overview]
Message-ID: <20120306080727.GA1641@x4> (raw)
In-Reply-To: <CADVnQyk_6LYW2nyjccWjv1NmjivXf5cXBqJ+LsZLjGyOj7kddQ@mail.gmail.com>
On 2012.03.06 at 00:46 -0500, Neal Cardwell wrote:
> On Wed, Feb 29, 2012 at 12:41 PM, Christian Kujau <lists@nerdbynature.de> wrote:
> > This is still happening with 3.3.0-rc5, .config & dmesg here:
> >
> > http://nerdbynature.de/bits/3.3.0-rc4/ipv4/
>
> I was finally able to reproduce this issue where there are warnings
> about sacked_out going negative (since 3.3.0-rc4), and my testing
> shows that this patch seems to fix the issue:
>
> http://patchwork.ozlabs.org/patch/144844/
>
> For folks who were seeing this problem and are so inclined, feel free
> to try the latest 3.3-rc6 kernel (or davem's "net" tree in git, if
> that's easier) with that patch applied, and let me know how it goes.
Thanks for tracking this down, Neal.
In my case it looks like the issue was an "once in a lifetime" event.
So no amount of testing would prove anything.
--
Markus
next prev parent reply other threads:[~2012-03-06 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 0:05 WARNING: at net/ipv4/tcp_input.c:3418 Christian Kujau
2012-02-27 0:10 ` Christian Kujau
[not found] ` <alpine.DEB.2.01.1202290929520.4930@trent.utfs.org>
2012-03-01 17:31 ` Neal Cardwell
2012-03-02 14:34 ` Neal Cardwell
2012-03-06 5:46 ` Neal Cardwell
2012-03-06 8:07 ` Markus Trippelsdorf [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-25 18:34 Markus Trippelsdorf
[not found] ` <CAGK4HS8bSF3y45Jgf3Vc0L1mGXt_vx1M2rDJoU8jPV6ZY8Dacw@mail.gmail.com>
2012-02-26 0:06 ` Vijay Subramanian
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=20120306080727.GA1641@x4 \
--to=markus@trippelsdorf.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=ncardwell@google.com \
--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;
as well as URLs for NNTP newsgroup(s).