netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
	Netfilter Core Team <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] ipset: add "inner" flag version support
Date: Wed, 10 Jul 2013 12:31:59 +0100	[thread overview]
Message-ID: <51DD462F.7050601@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1307081843001.28827@blackhole.kfki.hu>


Jozsef Kadlecsik wrote:
> On Mon, 8 Jul 2013, Jozsef Kadlecsik wrote:
>
>   
>> On Fri, 5 Jul 2013, Dash Four wrote:
>>
>>     
>>> This series of 2 patches supplements the previous version (v3) and adds
>>> "inner" flag version support to all registered ipset types
>>> (kernel + userspace).
>>>
>>> Dash Four (2):
>>>   ipset: add set match "inner" flag support
>>>   ipset (userspace): add "inner" flag version support
>>>       
>> All of your patches (including the previous series) are mangled and I'm 
>> unable to apply them. It seems there's an extra space at the beginning of 
>> every line starting with a whitespace character or something like that. 
>> Please check your patches and resubmit the fixed ones.
>>     
>
> Meanwhile, while looking at your code on how to extend it, I have noticed 
> two issues:
>
> - From ip_set_get_ip4_inner_hdr and ip_set_get_ip6_inner_hdr you pass back
>   the pointer to a local buffer, which is not good.
Why? By "local buffer" I take it you mean the ip header pointer, correct?

>  Please move the local
>   buffer definitions into all of the functions which call *_inner_hdr.
>
> - The second is an optimization issue: for two or more dimensional
>   sets the *_inner_hdr functions are called multiple times instead of 
>   once. *_inner_hdr functions should pass back the pointer to the IP
>   header/buffer (and use simple ip[46]addrptr inline functions on that) 
>   and set protooff for *get_port.
>
>   So it should be something like this:
>
> hash_ipportip4_kadt(...
> 	const struct hash_ipportip *h = set->data;
> 	ipset_adtfn adtfn = set->variant->adt[adt];
> 	struct hash_ipportip4_elem e = { };
> 	struct ip_set_ext ext = IP_SET_INIT_KEXT(skb, opt, h);
> 	struct iphdr _iph, *iph = &_iph;
> 	unsigned int protooff = ip_hdrlen(skb);
>
> 	if (!ip_set_get_ip4_inner_hdr(skb, &protooff, iph,
> 				opt->cmdflags & IPSET_FLAG_INNER) ||
> 	    !ip_set_get_ip4_port(skb, opt->flags & IPSET_DIM_TWO_SRC,
> 				 &e.port, &e.proto, protooff))
> 		return -EINVAL
>
> 	ip4addrptr(iph, opt->flags & IPSET_DIM_ONE_SRC, &e.ip);
> 	ip4addrptr(iph, opt->flags & IPSET_DIM_THREE_SRC, &e.ip2);
> 	...
>   
I'll look into this in the next few days - just in case you find 
something else you are unhappy with as I have time constraints and 
cannot afford to be churning out patches on a daily basis.


      reply	other threads:[~2013-07-10 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 22:23 [PATCH v4 0/2] ipset: add "inner" flag version support Dash Four
2013-07-08  7:50 ` Jozsef Kadlecsik
2013-07-08 17:02   ` Jozsef Kadlecsik
2013-07-10 11:31     ` Dash Four [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=51DD462F.7050601@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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).