From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000002c Date: Mon, 06 Feb 2012 10:19:50 +0100 Message-ID: <1328519990.2220.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> References: <20120201.162157.880976652659067010.davem@davemloft.net> <4F2A87B0.6070900@profihost.ag> <1328195055.2279.61.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20120202.143957.2251106530056768980.davem@davemloft.net> <20120203004228.GA23429@kroah.com> <4F2B8348.3090305@profihost.ag> <1328253972.2480.42.camel@edumazet-laptop> <4F2B963F.4020504@profihost.ag> <1328267097.2157.17.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> <20120203155309.GB20638@kroah.com> <4F2F9784.7090203@profihost.ag> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Greg KH , David Miller , jwboyer@gmail.com, hch@infradead.org, netdev@vger.kernel.org, david@fromorbit.com, stable@vger.kernel.org, gregkh@suse.de, Ilpo =?ISO-8859-1?Q?J=E4rvinen?= To: Stefan Priebe - Profihost AG Return-path: Received: from mail-we0-f174.google.com ([74.125.82.174]:49833 "EHLO mail-we0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754075Ab2BFJTy (ORCPT ); Mon, 6 Feb 2012 04:19:54 -0500 In-Reply-To: <4F2F9784.7090203@profihost.ag> Sender: netdev-owner@vger.kernel.org List-ID: Le lundi 06 f=C3=A9vrier 2012 =C3=A0 10:04 +0100, Stefan Priebe - Profi= host AG a =C3=A9crit : > Hi Eric, Hi David >=20 > today i've seen this: > [1048676.660457] ------------[ cut here ]------------ > [1048676.688131] WARNING: at net/ipv4/tcp_input.c:2964 > tcp_ack+0xfe1/0x2420() > [1048676.716291] Hardware name: X8SIL > [1048676.744292] Modules linked in: xt_tcpudp ipt_REJECT iptable_filt= er > ip_tables x_tables coretemp k8temp ipv6 dm_snapshot dm_mod > [1048676.802468] Pid: 0, comm: kworker/0:1 Not tainted 2.6.40.17.1int= el #1 > [1048676.831737] Call Trace: > [1048676.860455] [] ? tcp_ack+0xfe1/0x2420 > [1048676.860765] [] warn_slowpath_common+0x80/0xc0 > [1048676.860771] [] warn_slowpath_null+0x15/0x20 > [1048676.860777] [] tcp_ack+0xfe1/0x2420 > [1048676.860784] [] tcp_rcv_established+0x300/0x63= 0 > [1048676.860791] [] tcp_v4_do_rcv+0x154/0x2d0 > [1048676.860796] [] tcp_v4_rcv+0x6fb/0x880 > [1048676.860804] [] ip_local_deliver_finish+0x127/= 0x250 > [1048676.860810] [] ip_local_deliver+0x8d/0xa0 > [1048676.860815] [] ip_rcv_finish+0x172/0x340 > [1048676.860820] [] ip_rcv+0x275/0x2f0 > [1048676.860827] [] __netif_receive_skb+0x427/0x4a= 0 > [1048676.860832] [] netif_receive_skb+0x78/0x80 > [1048676.860837] [] napi_skb_finish+0x50/0x70 > [1048676.860842] [] napi_gro_receive+0xc5/0xd0 > [1048676.860851] [] e1000_receive_skb+0x56/0x70 > [1048676.860856] [] e1000_clean_rx_irq+0x22b/0x3d0 > [1048676.860862] [] e1000_clean+0xb2/0x2f0 > [1048676.860868] [] ? run_timer_softirq+0x3c/0x320 > [1048676.860873] [] net_rx_action+0x10a/0x2b0 > [1048676.860879] [] __do_softirq+0xd0/0x1c0 > [1048676.860887] [] call_softirq+0x1c/0x30 > [1048676.860895] [] do_softirq+0x55/0x90 > [1048676.860900] [] irq_exit+0xad/0xe0 > [1048676.860905] [] do_IRQ+0x64/0xe0 > [1048676.860910] [] common_interrupt+0x13/0x13 > [1048676.860913] [] ? > notifier_call_chain+0x3f/0x80 > [1048676.860926] [] ? intel_idle+0xb3/0x120 > [1048676.860931] [] ? intel_idle+0x95/0x120 > [1048676.860937] [] cpuidle_idle_call+0xdc/0x1a0 > [1048676.860942] [] cpu_idle+0xb1/0x110 > [1048676.860948] [] start_secondary+0x201/0x297 > [1048676.860953] ---[ end trace 4d27234ace919a1b ]--- >=20 > Any idea about that? Is it due to my custom patch being buggy or is i= t > anything you know which is missing in 3.0.X too? Thats the tcp_fastretrans_alert() if (WARN_ON(!tp->sacked_out && tp->fackets_out)) tp->fackets_out =3D 0; I dont know if some recent patch addressed this issue. CC Ilpo on this one.