All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, fw@strlen.de, kadlec@blackhole.kfki.hu
Subject: Re: [PATCH nf-next v3] netfilter: nf_defrag: Skip defrag if NOTRACK is set
Date: Mon, 08 Jan 2018 22:34:07 -0700	[thread overview]
Message-ID: <cb22f295786e536559cb57339a050eff@codeaurora.org> (raw)
In-Reply-To: <20180108133206.2uvpgoxa5qdywrzp@salvia>

On 2018-01-08 06:32, Pablo Neira Ayuso wrote:
> Hi Subash,
> 
> One more concern before this gets upstream.
> 
> Do you think we can turn this into an on/off knob instead?
> 
> I mean, I think it's good if you add a new
> NF_IP_PRI_RAW_BEFORE_DEFRAG and we place it into uapi.
> 
> I'm just worried about follow up patches from people asking to making
> this flexible in all other existing tables, I would like this does not
> happen :-).
> 
>> +
>> +static struct xt_table packet_raw = {
>>  	.name = "raw",
>>  	.valid_hooks =  RAW_VALID_HOOKS,
>>  	.me = THIS_MODULE,
>> @@ -70,6 +74,14 @@ static int __init iptable_raw_init(void)
>>  {
>>  	int ret;
>> 
>> +	if (priority < NF_IP_PRI_CONNTRACK_DEFRAG &&
>> +	    priority > NF_IP_PRI_FIRST) {
>> +		packet_raw.priority = priority;
>> +
>> +		pr_info("iptable_raw: Using custom rule priority=%d\n",
>                          ^^^^^^^^^^^^
> 
> Probably better if you add:
> 
>         #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> 
> in this patch while on this.
> 
> Thanks for your patience, we're almost there.

Hi Pablo

Sure, I can update these.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

      reply	other threads:[~2018-01-09  5:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  4:24 [PATCH nf-next v3] netfilter: nf_defrag: Skip defrag if NOTRACK is set Subash Abhinov Kasiviswanathan
2018-01-08 13:32 ` Pablo Neira Ayuso
2018-01-09  5:34   ` Subash Abhinov Kasiviswanathan [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=cb22f295786e536559cb57339a050eff@codeaurora.org \
    --to=subashab@codeaurora.org \
    --cc=fw@strlen.de \
    --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 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.