From mboxrd@z Thu Jan 1 00:00:00 1970 From: Meelis Roos Subject: Re: ipv4_get_l4proto: Frag of proto 17 Date: Sat, 1 Sep 2007 18:04:16 +0300 (EEST) Message-ID: References: <46D66D00.7060801@trash.net> <46D8F87A.1080604@trash.net> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: netdev@vger.kernel.org, Netfilter Development Mailinglist To: Patrick McHardy Return-path: Received: from smtp2.it.da.ut.ee ([193.40.5.67]:36051 "EHLO smtp2.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753380AbXIAPFP (ORCPT ); Sat, 1 Sep 2007 11:05:15 -0400 In-Reply-To: <46D8F87A.1080604@trash.net> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org > I'm guessing that its ICMP errors containing UDP fragments. > > Could you add a WARN_ON(1) to ipv4_get_l4proto() in > net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c to verify > this? Yes, it seems to be an ICMP error: WARNING: at net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c:93 ipv4_get_l4proto() [] show_trace_log_lvl+0x1a/0x2f [] show_trace+0x12/0x14 [] dump_stack+0x15/0x17 [] ipv4_get_l4proto+0x78/0xc0 [nf_conntrack_ipv4] [] nf_ct_get_tuplepr+0x45/0xae [nf_conntrack] [] icmp_error+0x185/0x1f6 [nf_conntrack_ipv4] [] nf_conntrack_in+0xc0/0x409 [nf_conntrack] [] ipv4_conntrack_in+0x11/0x13 [nf_conntrack_ipv4] [] nf_iterate+0x36/0x67 [] nf_hook_slow+0x57/0xd6 [] ip_rcv+0x1d9/0x489 [] netif_receive_skb+0x2c9/0x34a [] rtl8139_poll+0x2a5/0x410 [8139too] [] net_rx_action+0x56/0xd5 [] __do_softirq+0x38/0x7a [] do_softirq+0x41/0x91 ======================= ipv4_get_l4proto: Frag of proto 17 -- Meelis Roos (mroos@linux.ee)