Date: Sun, 2 Mar 2008 21:51:28 +0200 (EET)
From: "=?ISO-8859-1?Q?Ilpo_J=E4rvinen?=" <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()
In-Reply-To: <3d8471ca0803020515m1e4af9d9xd37a8912e58a4504@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.0803022145210.18020@kivilampi-30.cs.helsinki.fi>
References: <858077.97160.qm@web39709.mail.mud.yahoo.com> 
 <20080223000310.4630daa8.akpm@linux-foundation.org> 
 <Pine.LNX.4.64.0802271108290.13029@kivilampi-30.cs.helsinki.fi> 
 <3d8471ca0802271056l320a7ee2m5227e114a968d483@mail.gmail.com> 
 <Pine.LNX.4.64.0802272120430.1741@kivilampi-30.cs.helsinki.fi> 
 <Pine.LNX.4.64.0802281018480.32401@kivilampi-30.cs.helsinki.fi> 
 <3d8471ca0803020420ka42319bu1b9888217c869d9d@mail.gmail.com> 
 <Pine.LNX.4.64.0803021432200.17919@kivilampi-30.cs.helsinki.fi>
 <3d8471ca0803020515m1e4af9d9xd37a8912e58a4504@mail.gmail.com>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; boundary="-696243703-662713104-1204487187=:18020"
Content-ID: <Pine.LNX.4.64.0803022147040.18020@kivilampi-30.cs.helsinki.fi>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1647
Lines: 41

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---696243703-662713104-1204487187=:18020
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Content-ID: <Pine.LNX.4.64.0803022146411.18020@kivilampi-30.cs.helsinki.fi>

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.
---696243703-662713104-1204487187=:18020--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/