From: David Miller <davem@davemloft.net>
To: s.priebe@profihost.ag
Cc: ncardwell@google.com, eric.dumazet@gmail.com, greg@kroah.com,
stable@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 3.0.23 WARNING: at net/ipv4/tcp_input.c:3375 tcp_ack+0x1d62/0x2030()
Date: Mon, 19 Mar 2012 14:24:12 -0400 (EDT) [thread overview]
Message-ID: <20120319.142412.1284054436734248444.davem@davemloft.net> (raw)
In-Reply-To: <AB9F1763-96B1-4AE4-8D94-73246EA08207@profihost.ag>
From: Stefan Priebe <s.priebe@profihost.ag>
Date: Mon, 19 Mar 2012 19:20:39 +0100
> Am 19.03.2012 um 18:39 schrieb Neal Cardwell <ncardwell@google.com>:
>
>> On Mon, Mar 19, 2012 at 09:10:51AM +0100, Stefan Priebe - Profihost AG wrote:
>>> WARNING: at net/ipv4/tcp_input.c:3375 tcp_ack+0x1d62/0x2030()
>>
>> I double-checked the warning, and indeed in the 3.0.23 tcp_input.c at
>>
>> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=blob;f=net/ipv4/tcp_input.c;h=ee08f11ff21a802faa8b32efc1eb312e479878d6;hb=bf6a68d2a214e07f7c0d6538e00e17b826714160#l3375
>>
>> that line is:
>> WARN_ON((int)tp->sacked_out < 0);
>>
>> So this indeed looks like the known issue that is fixed by the commits
>> Eric mentions, which are in 3.0.25.
>>
>> neal
>
> Perfect, thanks!
>
> Greg any ETA?
He released it the very second he told you to use it.
next prev parent reply other threads:[~2012-03-19 18:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 8:10 3.0.23 WARNING: at net/ipv4/tcp_input.c:3375 tcp_ack+0x1d62/0x2030() Stefan Priebe - Profihost AG
2012-03-19 16:15 ` Greg KH
2012-03-19 16:16 ` Greg KH
2012-03-19 17:13 ` Eric Dumazet
2012-03-19 17:39 ` Neal Cardwell
2012-03-19 18:20 ` Stefan Priebe
2012-03-19 18:24 ` David Miller [this message]
2012-03-20 7:30 ` Stefan Priebe - Profihost AG
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=20120319.142412.1284054436734248444.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=greg@kroah.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=s.priebe@profihost.ag \
--cc=stable@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).