netdev - Re: Linux 3.6.x kernel crash in tcp_slow_start / bictcp_cong

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]

Message-ID: <20130123214445.GA16641@order.stressinduktion.org>
Date:	Wed, 23 Jan 2013 22:44:45 +0100
From:	Hannes Frederic Sowa <hannes@...essinduktion.org>
To:	Pasi Kärkkäinen <pasik@....fi>
Cc:	netdev@...r.kernel.org
Subject: Re: Linux 3.6.x kernel crash in tcp_slow_start / bictcp_cong_avoid with wfica

On Wed, Jan 23, 2013 at 06:12:38PM +0200, Pasi Kärkkäinen wrote:
> My laptop running Fedora 17 randomly crashes when using wfica (Citrix Receiver / ICA Client) 
> proprietary closed source client for accessing remote desktop server. 
> wfica is running as a normal user, so it shouldn't be able to cause a kernel crash. 
> 
> Crashes seem to happen most often when I use either wlan- or 3G mobile data Internet connection. 
> These kernel crashes happen ramdomly, often 1-2 times a week. 
> What usually happens is that I notice the Internet connection has died, 
> and when I check the kernel dmesg I'm seeing the traceback. 
> At this point I'm still able to use the gnome desktop for maybe 1-5 minutes, 
> but applications start to fail one by one, and finally everything just halts 
> and I need to power cycle the laptop. 

Would it be possible to capture a strace -e network, so we could see which
setsockopt combinations are being applied to the socket. Is capturing ss -ioem
in such moments still possible?

Thanks,

  Hannes

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