netdev - Re: WARNING: at net/ipv4/tcp_input.c:2539 tcp

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>] [day] [month] [year] [list]

Date:	Tue, 20 May 2008 16:28:07 +0300 (EEST)
From:	"Ilpo Järvinen" <ilpo.jarvinen@...sinki.fi>
To:	int 986 <int986@...il.com>
cc:	Netdev <netdev@...r.kernel.org>
Subject: Re: WARNING: at net/ipv4/tcp_input.c:2539 tcp_ack+0xd2b/0x191f()

On Mon, 19 May 2008, int 986 wrote:

> thank you for detailed explanation. Debug patch is unlikely to test on our
> live servers, but i can stress test it on our test servers.

Thanks, please take the latest debug patch from here:

  http://marc.info/?l=linux-netdev&m=120972551120080&w=2

Please make sure you have log enough buffer for kernel messages while 
testing (CONFIG_LOG_BUF_SHIFT) so that the disaster of the last time 
doesn't repeat... :-)

> We have farm with web servers for static content delivery and live
> streaming. Our servers are from the tiny one with two disks to large systems
> with 96 disks and external arrays. On every server we are using lighttpd
> 1.5svn and linux 2.6.25.3. This warning we are seeing on every server in our
> farm. I don't think that bug is connected to network setup may be is
> connected to lighttpd - because we are in six different co-locations and
> every co-location has your own network setup :)

Yeah, you may well be right, it could well be something else on the 
end-to-end path which causes it to trigger. ...I was just trying to find
a common denominator as the other guy has a setup which is know to reorder 
things.

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