netdev - Re: 2.6.25-rc8: WARNING: at net/ipv4/tcp_input.c:2173 tcp_mark_head

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0804031616330.21524@wrl-59.cs.helsinki.fi>
Date:	Thu, 3 Apr 2008 16:26:01 +0300 (EEST)
From:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To:	Soeren Sonnenburg <kernel@....de>
cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Netdev <netdev@...r.kernel.org>
Subject: Re: 2.6.25-rc8: WARNING: at net/ipv4/tcp_input.c:2173
 tcp_mark_head_lost+0x11d/0x150()

On Thu, 3 Apr 2008, Soeren Sonnenburg wrote:

> trying to download things, I am seeing this (ignore the tainted, it is
> from madwifi and although the module is loaded the device was never
> used)
> 
> Could anyone make sense of this please?

...I'm just trying to find out who and where invariants of the TCP code
are broken. These were relatively recently enabled (pre-2.6.24 just didn't 
care too much). A number of long standing issues plus bugs from my 
modifications have been fixed because of the more rigid checking :-).

> ------------[ cut here ]------------
> WARNING: at net/ipv4/tcp_input.c:2173 tcp_mark_head_lost+0x11d/0x150()

> ------------[ cut here ]------------
> WARNING: at net/ipv4/tcp_input.c:1771 tcp_enter_frto+0x267/0x270()

> ------------[ cut here ]------------
> WARNING: at net/ipv4/tcp_input.c:2532 tcp_ack+0x1a6f/0x1d60()

Can you reproduce it? 

Please include netdev next time while report networking related problems.


-- 
 i.


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html