netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: move ipv6_find_hdr to net/ipv6/netfilter.c and rename it
Date: Tue, 27 Nov 2012 01:59:28 +0100	[thread overview]
Message-ID: <20121127005928.GA20540@1984> (raw)
In-Reply-To: <alpine.LNX.2.01.1211251228320.26208@nerf07.vanv.qr>

On Sun, Nov 25, 2012 at 12:34:20PM +0100, Jan Engelhardt wrote:
> On Sunday 2012-11-25 00:07, pablo@netfilter.org wrote:
> 
> >From: Pablo Neira Ayuso <pablo@netfilter.org>
> >
> >IPVS uses ipv6_find_hdr, but this function is defined in ip6_tables.c,
> >to avoid such a dependency, move the function definition to the
> >generic IPv6 netfilter infrastructure.
> 
> Could we move this in a different way, such that the "ipv6_find_hdr"
> function and functions from exthdrs_core.c end up in a separate
> module (or even built-in code), such that modules like xt_socket.c
> can drop their dependency on ipv6.ko?

I'd go the other way around: we split xt_socket into two chunks so we
can avoid such IPv6 dependency.

> >index 429089c..d25f2d9 100644
> >--- a/net/ipv6/netfilter.c
> >+++ b/net/ipv6/netfilter.c
> >@@ -60,6 +60,109 @@ int ip6_route_me_harder(struct sk_buff *skb)
> > EXPORT_SYMBOL(ip6_route_me_harder);
> > 
> >+int nf_ip6_find_hdr(const struct sk_buff *skb, unsigned int *offset,
> >+		    int target, unsigned short *fragoff, int *flags)
> >+{
> >[...]
> >+}
> >+EXPORT_SYMBOL(nf_ip6_find_hdr);

      reply	other threads:[~2012-11-27  0:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24 23:07 [PATCH] netfilter: move ipv6_find_hdr to net/ipv6/netfilter.c and rename it pablo
2012-11-25 11:34 ` Jan Engelhardt
2012-11-27  0:59   ` Pablo Neira Ayuso [this message]

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=20121127005928.GA20540@1984 \
    --to=pablo@netfilter.org \
    --cc=jengelh@inai.de \
    --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).