From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 4/9] util: Add open_in_ns() helper
Date: Fri, 3 Nov 2023 11:20:33 +1100 [thread overview]
Message-ID: <ZUQ80ZzW50k3cpDb@zatzit> (raw)
In-Reply-To: <20231102190725.1c797252@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
On Thu, Nov 02, 2023 at 07:07:25PM +0100, Stefano Brivio wrote:
> On Thu, 5 Oct 2023 14:44:40 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > Most of our helpers which need to enter the pasta network namespace are
> > quite specialised. Add one which is rather general - it just open()s a
> > given file in the namespace context and returns the fd back to the main
> > namespace. This will have some future uses.
> >
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > ---
> > util.c | 39 +++++++++++++++++++++++++++++++++++++++
> > util.h | 1 +
> > 2 files changed, 40 insertions(+)
> >
> > diff --git a/util.c b/util.c
> > index a8f3b35..92ad375 100644
> > --- a/util.c
> > +++ b/util.c
> > @@ -364,6 +364,45 @@ bool ns_is_init(void)
> > return ret;
> > }
> >
> > +struct open_in_ns_args {
>
> It would be nice to have the usual kerneldoc-style comment to this
> (at a first reading: are "flags" the flags for open(2) or something
> specialised for internal use?).
>
> > + const struct ctx *c;
> > + int fd;
> > + int err;
> > + const char *path;
> > + int flags;
> > +};
> > +
> > +static int do_open_in_ns(void *arg)
>
> Same for this one.
Eh, ok. I left it out originally, because they both seemed like they
were essentially internals of open_in_ns() itself, but I've added them
now.
>
> The rest of the series makes sense and looks good to me.
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-03 0:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 3:44 [PATCH 0/9] Clean ups to automatic port forwarding David Gibson
2023-10-05 3:44 ` [PATCH 1/9] conf: Cleaner initialisation of default forwarding modes David Gibson
2023-10-05 3:44 ` [PATCH 2/9] port_fwd: Move automatic port forwarding code to port_fwd.[ch] David Gibson
2023-10-05 3:44 ` [PATCH 3/9] port_fwd: Better parameterise procfs_scan_listen() David Gibson
2023-11-02 18:07 ` Stefano Brivio
2023-11-03 0:16 ` David Gibson
2023-10-05 3:44 ` [PATCH 4/9] util: Add open_in_ns() helper David Gibson
2023-11-02 18:07 ` Stefano Brivio
2023-11-03 0:20 ` David Gibson [this message]
2023-10-05 3:44 ` [PATCH 5/9] port_fwd: Pre-open /proc/net/* files rather than on-demand David Gibson
2023-10-05 3:44 ` [PATCH 6/9] port_fwd: Don't NS_CALL get_bound_ports() David Gibson
2023-10-05 3:44 ` [PATCH 7/9] port_fwd: Split TCP and UDP cases for get_bound_ports() David Gibson
2023-10-05 3:44 ` [PATCH 8/9] port_fwd: Move port scanning /proc fds into struct port_fwd David Gibson
2023-10-05 3:44 ` [PATCH 9/9] port_fwd: Simplify get_bound_ports_*() to port_fwd_scan_*() David Gibson
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=ZUQ80ZzW50k3cpDb@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).