From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira <pablo@eurodev.net>
Cc: Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Harald Welte <laforge@netfilter.org>
Subject: Re: [PATCH] ip_queue and fragments
Date: Thu, 05 Aug 2004 16:16:34 +0200 [thread overview]
Message-ID: <41124142.3030600@trash.net> (raw)
In-Reply-To: <411236FF.4080405@eurodev.net>
Pablo Neira wrote:
> Hi,
>
> I've tracing ip_queue source code and I think that it's not fragment
> aware. Am I missing anything?
This check prevents copying data outside of skb->data:
case IPQ_COPY_PACKET:
if (copy_range == 0 || copy_range > entry->skb->len)
data_len = entry->skb->len;
else
data_len = copy_range;
skb_copy_bits always stays inside limits if len is positive, so you can
do something like this:
if (copy_range == 0)
data_len = ~0UL;
else
data_len = copy_range;
but you have to remove the jump to nlmsg_failure when skb_copy_bits fails.
Regards
Patrick
>------------------------------------------------------------------------
>
>diff -u -r1.1.1.1 ip_queue.c
>--- a/net/ipv4/netfilter/ip_queue.c 11 May 2004 13:07:08 -0000 1.1.1.1
>+++ b/net/ipv4/netfilter/ip_queue.c 4 Aug 2004 14:37:25 -0000
>@@ -255,9 +255,10 @@
> entry->skb->dev->hard_header_parse(entry->skb,
> pmsg->hw_addr);
> }
>-
>- if (data_len)
>- memcpy(pmsg->payload, entry->skb->data, data_len);
>+
>+ if (data_len)
>+ if (skb_copy_bits(entry->skb, 0, pmsg->payload, data_len) != 0)
>+ goto nlmsg_failure;
>
> nlh->nlmsg_len = skb->tail - old_tail;
> return skb;
>
>
next prev parent reply other threads:[~2004-08-05 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 13:32 [PATCH] ip_queue and fragments Pablo Neira
2004-08-05 14:16 ` Patrick McHardy [this message]
2004-08-06 16:44 ` Pablo Neira
2004-08-07 19:20 ` 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=41124142.3030600@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@eurodev.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.