LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Guillaume Chazarain <guichaz@gmail.com>,
	Ray Lee <ray-lk@madrabbit.org>, Chris Wedgwood <cw@f00f.org>
Cc: Giangiacomo Mariotti <giangiacomo_mariotti@yahoo.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: WARNING: at net/ipv4/tcp_input.c:2054 tcp_mark_head_lost()
Date: Sun, 2 Mar 2008 21:51:28 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0803022145210.18020@kivilampi-30.cs.helsinki.fi> (raw)
In-Reply-To: <3d8471ca0803020515m1e4af9d9xd37a8912e58a4504@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1011 bytes --]

On Sun, 2 Mar 2008, Guillaume Chazarain wrote:

>> On Sun, Mar 2, 2008 at 1:38 PM, Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> wrote:
>>> It does not contain any "KERNEL: assertion (packets <=
>> > tp->packets_out) failed at" line, so I'm afraid it's just noise.

Doh, you were right in this one...

>>  At least it catches one bug which could cause that assertion (it is much
>>  more rigid than the assertion and thus it catched it even though you
>>  won't see that assertion to ever trigger :-)).
>
> Great :-)

...I spoke too early, it was just that the verify call was placed into
a place where the fackets_out is not yet reduced (I had too many version 
of that patch when I first did that and probably picked wrong one of 
them as a starting point, I'm sorry about that). I'll send an updated 
patch tomorrow for you and also correct it so that I don't need to ask 
things like this again (as long as one pastes couple of first occuring 
stacktraces):

>>>  Could you next figure out what is at:


-- 
 i.

  reply	other threads:[~2008-03-02 19:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  4:04 Giangiacomo Mariotti
2008-02-23  8:03 ` Andrew Morton
2008-02-27  9:29   ` Ilpo Järvinen
2008-02-27 18:56     ` Guillaume Chazarain
2008-02-27 19:29       ` Ilpo Järvinen
2008-02-28  8:22         ` Ilpo Järvinen
2008-02-29  1:10           ` Andrew Morton
2008-02-29  4:35             ` Bill Fink
2008-02-29 12:24               ` Ilpo Järvinen
2008-03-02 12:20           ` Guillaume Chazarain
2008-03-02 12:38             ` Ilpo Järvinen
2008-03-02 13:15               ` Guillaume Chazarain
2008-03-02 19:51                 ` Ilpo Järvinen [this message]
2008-03-03  8:32                   ` Ilpo Järvinen
2008-03-03 13:40                     ` Ilpo Järvinen
2008-03-03 13:53                       ` [PATCH net-2.6] [TCP]: Must count fack_count also when skipping Ilpo Järvinen
2008-03-03 20:11                         ` David Miller
2008-03-24 20:36                         ` Frederik Himpe
2008-03-24 21:41                           ` David Miller
2008-03-25 21:24                             ` Ilpo Järvinen
2008-03-26  3:05                               ` David Miller

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=Pine.LNX.4.64.0803022145210.18020@kivilampi-30.cs.helsinki.fi \
    --to=ilpo.jarvinen@helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=cw@f00f.org \
    --cc=giangiacomo_mariotti@yahoo.com \
    --cc=guichaz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ray-lk@madrabbit.org \
    --subject='Re: WARNING: at net/ipv4/tcp_input.c:2054 tcp_mark_head_lost()' \
    /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

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).