public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 04/14] nstool: Split some command line parsing and socket setup to subcommands
Date: Wed, 5 Apr 2023 13:58:00 +0200	[thread overview]
Message-ID: <20230405135800.1c3705ca@elisabeth> (raw)
In-Reply-To: <20230404014638.3225556-5-david@gibson.dropbear.id.au>

On Tue,  4 Apr 2023 11:46:28 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> This will make it easier to differentiate the options to those commands
> further in future.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
>  test/nstool.c | 102 +++++++++++++++++++++++++++++++++-----------------
>  1 file changed, 68 insertions(+), 34 deletions(-)
> 
> diff --git a/test/nstool.c b/test/nstool.c
> index 7e069b6..9ea7eeb 100644
> --- a/test/nstool.c
> +++ b/test/nstool.c
> @@ -11,6 +11,7 @@
>  #include <stdio.h>
>  #include <stdlib.h>
>  #include <string.h>
> +#include <stdbool.h>
>  #include <errno.h>
>  #include <unistd.h>
>  #include <sys/socket.h>
> @@ -37,19 +38,55 @@ static void usage(void)
>  	    "    terminate.\n");
>  }
>  
> -static void hold(int fd, const struct sockaddr_un *addr)
> +static int connect_ctl(const char * sockpath, bool wait)
>  {
> +	int fd = socket(AF_UNIX, SOCK_STREAM, PF_UNIX);
> +	struct sockaddr_un addr = {
> +		.sun_family = AF_UNIX,
> +	};
>  	int rc;
>  
> -	rc = bind(fd, (struct sockaddr *)addr, sizeof(*addr));
> +	if (fd < 0)
> +		die("socket(): %s\n", strerror(errno));

Unrelated: it would be nice if die() added newlines eventually.

> +
> +	strncpy(addr.sun_path, sockpath, UNIX_PATH_MAX);
> +
> +	do {
> +		rc = connect(fd, (struct sockaddr *)&addr, sizeof(addr));
> +		if (rc < 0 &&
> +		    (!wait || (errno != ENOENT && errno != ECONNREFUSED)))
> +			die("connect() to %s: %s\n", sockpath, strerror(errno));

A (1ms?) delay would be nice to have here -- it's almost a busyloop,
connect() fails fast.

> +	} while (rc < 0);
> +
> +	return fd;
> +}
> +
> +static void cmd_hold(int argc, char *argv[])
> +{
> +	int fd = socket(AF_UNIX, SOCK_STREAM, PF_UNIX);
> +	struct sockaddr_un addr = {
> +		.sun_family = AF_UNIX,
> +	};
> +	const char *sockpath = argv[1];
> +	int rc;
> +
> +	if (argc != 2)
> +		usage();
> +
> +	if (fd < 0)
> +		die("socket(): %s\n", strerror(errno));
> +
> +	strncpy(addr.sun_path, sockpath, UNIX_PATH_MAX);
> +
> +	rc = bind(fd, (struct sockaddr *)&addr, sizeof(addr));
>  	if (rc < 0)
> -		die("bind(): %s\n", strerror(errno));
> +		die("bind() to %s: %s\n", sockpath, strerror(errno));
>  
>  	rc = listen(fd, 0);
>  	if (rc < 0)
> -		die("listen(): %s\n", strerror(errno));
> +		die("listen() on %s: %s\n", sockpath, strerror(errno));
>  
> -	printf("nstool: local PID=%d  local UID=%u  local GID=%u\n",
> +	printf("nstool hold: local PID=%d  local UID=%u  local GID=%u\n",
>  	       getpid(), getuid(), getgid());
>  	do {
>  		int afd = accept(fd, NULL, NULL);
> @@ -63,71 +100,68 @@ static void hold(int fd, const struct sockaddr_un *addr)
>  			die("read(): %s\n", strerror(errno));
>  	} while (rc == 0);
>  
> -	unlink(addr->sun_path);
> +	unlink(sockpath);
>  }
>  
> -static void pid(int fd, const struct sockaddr_un *addr)
> +static void cmd_pid(int argc, char *argv[])
>  {
> -	int rc;
> +	const char *sockpath = argv[1];
>  	struct ucred peercred;
>  	socklen_t optlen = sizeof(peercred);
> +	int fd, rc;
>  
> -	do {
> -		rc = connect(fd, (struct sockaddr *)addr, sizeof(*addr));
> -		if (rc < 0 && errno != ENOENT && errno != ECONNREFUSED)
> -			die("connect(): %s\n", strerror(errno));
> -	} while (rc < 0);
> +	if (argc != 2)
> +		usage();
> +
> +	fd = connect_ctl(sockpath, true);

I didn't spot this earlier, but... does it really make sense to wait in
cmd_pid(), also on ENOENT, rather than making 'hold' return only once
the socket is ready? I don't think it would be outrageous to have
'nstool pid' failing if the holding process doesn't exist.

Admittely, I'm biased by the few hundreds of times I needed to
'killall -9 nsholder' in the past months. :)

>  
>  	rc = getsockopt(fd, SOL_SOCKET, SO_PEERCRED,
>  			&peercred, &optlen);
>  	if (rc < 0)
> -		die("getsockopet(SO_PEERCRED): %s\n", strerror(errno));
> +		die("getsockopet(SO_PEERCRED) %s: %s\n",
> +		    sockpath, strerror(errno));
>  
>  	close(fd);
>  
>  	printf("%d\n", peercred.pid);
>  }
>  
> -static void stop(int fd, const struct sockaddr_un *addr)
> +static void cmd_stop(int argc, char *argv[])
>  {
> -	int rc;
> +	const char *sockpath = argv[1];
> +	int fd, rc;
>  	char buf = 'Q';
>  
> -	rc = connect(fd, (struct sockaddr *)addr, sizeof(*addr));
> -	if (rc < 0)
> -		die("connect(): %s\n", strerror(errno));
> +	if (argc != 2)
> +		usage();
> +
> +	fd = connect_ctl(sockpath, false);
>  
>  	rc = write(fd, &buf, sizeof(buf));

Unrelated: a compound literal would make this more readable.

-- 
Stefano


  reply	other threads:[~2023-04-05 11:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04  1:46 [PATCH 00/14] Improved tool for testing across multiple namespaces David Gibson
2023-04-04  1:46 ` [PATCH 01/14] nstool: Rename nsholder to nstool David Gibson
2023-04-04  1:46 ` [PATCH 02/14] nstool: Reverse parameters " David Gibson
2023-04-04  1:46 ` [PATCH 03/14] nstool: Move description of its operation modes from comment to usage David Gibson
2023-04-05 11:56   ` Stefano Brivio
2023-04-06  0:10     ` David Gibson
2023-04-04  1:46 ` [PATCH 04/14] nstool: Split some command line parsing and socket setup to subcommands David Gibson
2023-04-05 11:58   ` Stefano Brivio [this message]
2023-04-06  2:31     ` David Gibson
2023-04-06  6:47       ` Stefano Brivio
2023-04-06 10:35         ` David Gibson
2023-04-04  1:46 ` [PATCH 05/14] nstool: Replace "pid" subcommand with "info" subcommand David Gibson
2023-04-05 11:58   ` Stefano Brivio
2023-04-06  0:13     ` David Gibson
2023-04-04  1:46 ` [PATCH 06/14] nstool: Detect what namespaces target is in David Gibson
2023-04-05 11:58   ` Stefano Brivio
2023-04-06  0:15     ` David Gibson
2023-04-04  1:46 ` [PATCH 07/14] nstool: Add magic number to advertized information David Gibson
2023-04-05 11:58   ` Stefano Brivio
2023-04-06  0:18     ` David Gibson
2023-04-04  1:46 ` [PATCH 08/14] nstool: Helpers to iterate through namespace types David Gibson
2023-04-05 11:58   ` Stefano Brivio
2023-04-06  0:55     ` David Gibson
2023-04-04  1:46 ` [PATCH 09/14] nstool: Add nstool exec command to execute commands in an nstool namespace David Gibson
2023-04-05 11:58   ` Stefano Brivio
2023-04-06  0:59     ` David Gibson
2023-04-04  1:46 ` [PATCH 10/14] nstool: Add --keep-caps option to nstool exec David Gibson
2023-04-05 11:59   ` Stefano Brivio
2023-04-06  1:11     ` David Gibson
2023-04-04  1:46 ` [PATCH 11/14] test: Initialise ${TRACE} properly David Gibson
2023-04-04  1:46 ` [PATCH 12/14] test: Use "nstool exec" to slightly simplify tests David Gibson
2023-04-05 11:59   ` Stefano Brivio
2023-04-06  1:14     ` David Gibson
2023-04-04  1:46 ` [PATCH 13/14] nstool: Advertise the holder's cwd (in its mountns) across the socket David Gibson
2023-04-04  1:46 ` [PATCH 14/14] nstool: Enter holder's cwd when changing mount ns with nstool exec David Gibson
2023-04-05 12:01 ` [PATCH 00/14] Improved tool for testing across multiple namespaces Stefano Brivio

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=20230405135800.1c3705ca@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    /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).