From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCHv2] netfilter: Remove skb_is_nonlinear check from nf_conntrack_sip
Date: Fri, 14 May 2010 12:26:01 -0600 [thread overview]
Message-ID: <20100514182601.GJ15969@obsidianresearch.com> (raw)
In-Reply-To: <4BED92AF.50704@trash.net>
On Fri, May 14, 2010 at 08:13:03PM +0200, Patrick McHardy wrote:
> Your patch is based on an old version, the current version also
> supports TCP. I'll commit this patch to my tree after some testing.
Thanks!
> diff --git a/net/netfilter/nf_conntrack_sip.c b/net/netfilter/nf_conntrack_sip.c
> index b20f427..45750cc 100644
> +++ b/net/netfilter/nf_conntrack_sip.c
> @@ -1393,10 +1393,8 @@ static int sip_help_tcp(struct sk_buff *skb, unsigned int protoff,
>
> nf_ct_refresh(ct, skb, sip_timeout * HZ);
>
> - if (skb_is_nonlinear(skb)) {
> - pr_debug("Copy of skbuff not supported yet.\n");
> + if (unlikely(skb_linearize(skb)))
> return NF_ACCEPT;
> - }
Should this be NF_DROP? As I understand it skb_linearize only failes
if it runs out of memory, which probably means dropping is OK. But
passing a packet that might need rewriting could be harmful..
Jason
next prev parent reply other threads:[~2010-05-14 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 18:01 [PATCHv2] netfilter: Remove skb_is_nonlinear check from nf_conntrack_sip Jason Gunthorpe
2010-05-14 18:13 ` Patrick McHardy
2010-05-14 18:26 ` Jason Gunthorpe [this message]
2010-05-14 18:42 ` Patrick McHardy
2010-05-14 19:26 ` Patrick McHardy
2010-05-14 19:33 ` Jan Engelhardt
2010-05-14 19:41 ` Patrick McHardy
2010-05-14 19:56 ` Jason Gunthorpe
2010-05-14 18:33 ` Jan Engelhardt
2010-05-14 18:45 ` 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=20100514182601.GJ15969@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).