netdev - Re: Assertions in latest kernels

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

Date:	Tue, 22 Jan 2008 23:57:23 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	krkumar2@...ibm.com
Cc:	netdev@...r.kernel.org
Subject: Re: Assertions in latest kernels

From: Krishna Kumar2 <krkumar2@...ibm.com>
Date: Wed, 23 Jan 2008 13:22:05 +0530

> Sorry for the duplicate bug report, I just saw that Dave Young had already
> reported three of the
> 4 assertions that I was getting. The only different assert I am getting is:
> 
> iperf with multiple threads almost always gets these 4, *especially* when I
> do some batching :).
> 
> static void tcp_fastretrans_alert(struct sock *sk, int pkts_acked, int flag)
> {
>       ...
>       if (WARN_ON(!tp->sacked_out && tp->fackets_out))
>             tp->fackets_out = 0;
>       ...
> }

Does this assertion show up first or do you get the other TCP
ones first?  It might be important, in that if you get the
others ones first that corrupted state might be what leads to
this one.

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