All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
	Netfilter Development Mailing list
	<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH v2] extensions: libxt_NFQUEUE: Add translation to nft
Date: Mon, 8 Feb 2016 10:29:49 +0100	[thread overview]
Message-ID: <20160208092949.GC32181@breakpoint.cc> (raw)
In-Reply-To: <CAKHNQQGy8EDrMbPQb2Og_Dk8wf62GaeKq1zO+uz2UB6HbZ9hAQ@mail.gmail.com>

Shivani Bhardwaj <shivanib134@gmail.com> wrote:
> On Sun, Feb 7, 2016 at 2:55 PM, Florian Westphal <fw@strlen.de> wrote:

> > Seems this could be written similar to something like:
> >
> > if (info->flags & NFQ_FLAG_CPU_FANOUT) {
> >         bool sep_needed = info->bypass & NFQ_FLAG_BYPASS;
> >         xt_xlate_add(xl, "%sfanout ", sep_need ? "," : "");
> > ...
> 
> The pointer info used in both the versions (of NFQUEUE_xlate) is for
> different structures. Sadly, this doesn't work as v3 structure doesn't
> have a member for bypass field.

Oh, right.  However bypass & flags overlap -- I think you could just use
info->flags & NFQ_FLAG_BYPASS.

If you look at NFQUEUE_parse_v3() it just calls NFQUEUE_parse_v2() with
the v3 structure.

  reply	other threads:[~2016-02-08  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07  6:07 [PATCH v2] extensions: libxt_NFQUEUE: Add translation to nft Shivani Bhardwaj
2016-02-07  9:25 ` Florian Westphal
2016-02-07 15:11   ` Shivani Bhardwaj
2016-02-08  9:29     ` Florian Westphal [this message]
2016-02-09  8:51       ` Shivani Bhardwaj

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=20160208092949.GC32181@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=shivanib134@gmail.com \
    /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.