From: Patrick McHardy <kaber@trash.net>
To: Nir Tzachar <nir.tzachar@gmail.com>
Cc: linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: WARNING: at net/ipv4/netfilter/nf_nat_standalone.c:89 nf_nat_fn+0x33/0x155()
Date: Fri, 10 Oct 2008 15:51:49 +0200 [thread overview]
Message-ID: <48EF5DF5.7070708@trash.net> (raw)
In-Reply-To: <9b2db90b0810092324o729e29c0i2e654c812592bbd2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
Nir Tzachar wrote:
> Hello.
>
> The following warning is reproducible with the code below on 2.6.25.6,
> which uses sendmsg on a udp socket using two iovecs:
>
> ....
> And I always get the following warning twice:
>
> [ 6658.338116] ------------[ cut here ]------------
> [ 6658.338121] WARNING: at net/ipv4/netfilter/nf_nat_standalone.c:89
> nf_nat_fn+0x33/0x155()
Thanks for the report. Does this patch fix it?
[-- Attachment #2: x --]
[-- Type: text/plain, Size: 589 bytes --]
diff --git a/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c b/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c
index 5a955c4..5bd4833 100644
--- a/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c
+++ b/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4.c
@@ -92,7 +92,7 @@ static int ipv4_get_l4proto(const struct sk_buff *skb, unsigned int nhoff,
/* Conntrack defragments packets, we might still see fragments
* inside ICMP packets though. */
- if (iph->frag_off & htons(IP_OFFSET))
+ if (iph->frag_off & htons(IP_MF | IP_OFFSET))
return -NF_DROP;
*dataoff = nhoff + (iph->ihl << 2);
next prev parent reply other threads:[~2008-10-10 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 6:24 WARNING: at net/ipv4/netfilter/nf_nat_standalone.c:89 nf_nat_fn+0x33/0x155() Nir Tzachar
2008-10-10 13:51 ` Patrick McHardy [this message]
2008-10-10 13:52 ` Patrick McHardy
2008-10-10 14:13 ` Patrick McHardy
[not found] <9b2db90b0810101349y7e357ef7g9c53f2ecf19fe3eb@mail.gmail.com>
2008-10-10 20:50 ` Nir Tzachar
2008-10-13 13:44 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48EF5DF5.7070708@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nir.tzachar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox