From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Rodrigo Partearroyo González" <rpartearroyo@albentia.com>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Iratxo Pichel Ortiz" <ipichel@albentia.com>,
"Noelia Morón" <nmoron@albentia.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: net/sched/act_nat.c BUG
Date: Fri, 09 Jul 2010 17:13:40 +0200 [thread overview]
Message-ID: <1278688420.2696.7.camel@edumazet-laptop> (raw)
In-Reply-To: <201007091637.57660.rpartearroyo@albentia.com>
Le vendredi 09 juillet 2010 à 16:37 +0200, Rodrigo Partearroyo González
a écrit :
> Hi all,
>
> I have been testing Stateless NAT and found that ICMP packets with length less
> than 20 bytes were not correctly NAT'ed. I have found a BUG that makes taking
> into account IP header length twice, so ICMP packets smaller than 20 bytes
> were being dropped.
>
CC netdev
> The proposed fix is:
>
> Index: net/sched/act_nat.c
> ===================================================================
> --- net/sched/act_nat.c
> +++ net/sched/act_nat.c
> @@ -202,7 +202,7 @@
> {
> struct icmphdr *icmph;
>
> - if (!pskb_may_pull(skb, ihl + sizeof(*icmph) + sizeof(*iph)))
> + if (!pskb_may_pull(skb, ihl + sizeof(*icmph)))
> goto drop;
>
> icmph = (void *)(skb_network_header(skb) + ihl);
>
> Please, consider applying it.
Nice catch, but take a look at next lines too,
when call to skb_clone_writable() is done, since same error is present.
skb_clone_writable(skb,
ihl + sizeof(*icmph) + sizeof(*iph))
Please submit a formal patch, with your "Signed-off-by: ...", as
documented in Documentation/SubmittingPatches
Thanks
next parent reply other threads:[~2010-07-09 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201007091637.57660.rpartearroyo@albentia.com>
2010-07-09 15:13 ` Eric Dumazet [this message]
2010-07-09 23:23 ` net/sched/act_nat.c BUG Herbert Xu
2010-07-10 0:00 ` David Miller
2010-07-10 6:27 ` Eric Dumazet
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=1278688420.2696.7.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=ipichel@albentia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nmoron@albentia.com \
--cc=rpartearroyo@albentia.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