From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft 1/3] libnftables: add nft_ctx_set_netns()
Date: Sun, 12 Jan 2020 11:28:03 +0100 [thread overview]
Message-ID: <20200112102802.7bvwieqaza3zdbza@salvia> (raw)
In-Reply-To: <20200110125311.GP20229@orbyte.nwl.cc>
On Fri, Jan 10, 2020 at 01:53:11PM +0100, Phil Sutter wrote:
> Hi Pablo,
>
> On Thu, Jan 09, 2020 at 06:21:13PM +0100, Pablo Neira Ayuso wrote:
> [...]
> > diff --git a/include/nftables/libnftables.h b/include/nftables/libnftables.h
> > index 765b20dd71ee..887628959ac6 100644
> > --- a/include/nftables/libnftables.h
> > +++ b/include/nftables/libnftables.h
> > @@ -34,10 +34,13 @@ enum nft_debug_level {
> > * Possible flags to pass to nft_ctx_new()
> > */
> > #define NFT_CTX_DEFAULT 0
> > +#define NFT_CTX_NETNS 1
>
> What is this needed for?
The socket is initialized from nft_ctx_init(), and such initialization
needs to happen after the netns switch.
> > struct nft_ctx *nft_ctx_new(uint32_t flags);
> > void nft_ctx_free(struct nft_ctx *ctx);
> >
> > +int nft_ctx_set_netns(struct nft_ctx *ctx, const char *netns);
>
> Is there a way to select init ns again?
AFAIK, setns() does not let you go back to init ns once set.
next prev parent reply other threads:[~2020-01-12 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 17:21 [PATCH nft 0/3] netns support Pablo Neira Ayuso
2020-01-09 17:21 ` [PATCH nft 1/3] libnftables: add nft_ctx_set_netns() Pablo Neira Ayuso
2020-01-10 12:53 ` Phil Sutter
2020-01-12 10:28 ` Pablo Neira Ayuso [this message]
2020-01-12 10:40 ` Pablo Neira Ayuso
2020-01-14 10:25 ` Phil Sutter
2020-01-14 10:38 ` Pablo Neira Ayuso
2020-01-14 17:04 ` Phil Sutter
2020-01-09 17:21 ` [PATCH nft 2/3] main: split parsing from libnftables initialization Pablo Neira Ayuso
2020-01-09 17:21 ` [PATCH nft 3/3] main: add -w/--netns option Pablo Neira Ayuso
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=20200112102802.7bvwieqaza3zdbza@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).