[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <46D99105.8030302@trash.net>
Date: Sat, 01 Sep 2007 18:19:17 +0200
From: Patrick McHardy <kaber@...sh.net>
To: Meelis Roos <mroos@...ux.ee>
CC: netdev@...r.kernel.org,
Netfilter Development Mailinglist
<netfilter-devel@...ts.netfilter.org>,
"David S. Miller" <davem@...emloft.net>,
Yasuyuki KOZAKAI <yasuyuki.kozakai@...hiba.co.jp>
Subject: Re: ipv4_get_l4proto: Frag of proto 17
Meelis Roos wrote:
>>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()
> [<c0103447>] show_trace_log_lvl+0x1a/0x2f
> [<c0103f2e>] show_trace+0x12/0x14
> [<c0103f45>] dump_stack+0x15/0x17
> [<f8cc60fc>] ipv4_get_l4proto+0x78/0xc0 [nf_conntrack_ipv4]
> [<f8d14fc4>] nf_ct_get_tuplepr+0x45/0xae [nf_conntrack]
> [<f8cc6777>] icmp_error+0x185/0x1f6 [nf_conntrack_ipv4]
Thanks for testing. This patch removes the error message since its
perfectly valid for ICMP tracking to hand in a fragmented packet.
View attachment "x" of type "text/plain" (1554 bytes)
Powered by blists - more mailing lists