public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Paul Holzinger <pholzing@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] pasta: wait for netns setup before calling exec
Date: Thu, 2 Feb 2023 16:23:53 +0100	[thread overview]
Message-ID: <7799b65a-dd26-c198-721e-ef54b6756d7e@redhat.com> (raw)
In-Reply-To: <20230202112506.187d852e@elisabeth>


On 02/02/2023 11:25, Stefano Brivio wrote:
> On Wed,  1 Feb 2023 19:01:16 +0100
> Paul Holzinger <pholzing@redhat.com> wrote:
>
>> When a user spawns a command with pasta they expect the network to be
>> ready. Currently this does not work because pasta will fork/exec
>> before it will setup the network config.
>>
>> This patch fixes it by using a pipe to sync parent and child. The child
>> will now block reading from this pipe before the exec call. The parent
>> will then unblock the child only after the netns was configured.
> Thanks for the patch! I'm reviewing this in a bit.
>
> A few considerations meanwhile:
>
> - there's actually a bigger issue (you're fixing here) than the
>    namespace configuration (via netlink) itself: the tap device isn't
>    ready (tap_sock_init() hasn't been called yet) when we spawn the
>    command in the new namespace. Oops.
>
>    If you're wondering: we can't just reorder things, because to complete
>    the configuration phase (conf()) we need the namespace to be set up,
>    and we can't initialise the tap device before it's set up
>
> - pipes are more commonly used to transfer data around (hence the whole
>    code you need to open a communication channel, check it, close it).
>    Did you try with a signal? Or is there a reason why it wouldn't work?
>
>    You could simply SIGSTOP the child, from the child itself:
>
> 	kill(getpid(), SIGSTOP);
>
>    and send a SIGCONT to it (we already store the PID of the child in
>    pasta_child_pid) once we're ready.
>
>    SIGCONT is special in that it doesn't need CAP_KILL or the processes
>    to run under the same UID -- just in the same session, so it wouldn't
>    risk interfering with the isolation_*() calls.
>
>    I haven't tested this but I think it should lead to simpler code.
>
I simply haven't thought of using the stop signal, we use pipes like that
in podman so I knew how to implement it.
I will test your approach, I agree that it would be a bit simpler.


  reply	other threads:[~2023-02-02 15:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 18:01 [PATCH] pasta: wait for netns setup before calling exec Paul Holzinger
2023-02-02 10:25 ` Stefano Brivio
2023-02-02 15:23   ` Paul Holzinger [this message]
2023-02-03 14:44   ` Paul Holzinger
2023-02-03 16:37     ` Stefano Brivio
2023-02-03 18:55       ` Stefano Brivio
2023-02-06 19:53         ` Paul Holzinger
2023-02-07 10:55           ` Stefano Brivio
2023-02-07 19:09             ` Paul Holzinger
2023-02-08 13:01               ` Stefano Brivio
2023-02-08 15:06                 ` Paul Holzinger

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=7799b65a-dd26-c198-721e-ef54b6756d7e@redhat.com \
    --to=pholzing@redhat.com \
    --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).