public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 2/5] tap: Support for detection of existing sockets on ramfs
Date: Tue, 1 Nov 2022 11:41:12 +1100	[thread overview]
Message-ID: <Y2BrKND+LQfs3EAv@yekko> (raw)
In-Reply-To: <20221031112059.170269-3-sbrivio@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]

On Mon, Oct 31, 2022 at 12:20:56PM +0100, Stefano Brivio wrote:
> On ramfs, connecting to a non-existent UNIX domain socket yields
> EACCESS, instead of ENOENT. This is visible if we use passt directly
> on rootfs (a ramfs instance) from an initramfs image.
> 
> It's probably wrong for ramfs to return EACCES, but given the
> simplicity of the filesystem, I doubt we should try to fix it there
> at the possible cost of added complexity.

Yeah, that's deeply weird.  I'm not even sure how you'd get such a bug
involving the intersection of filesystem and unix socket.

> Also, this whole beauty should go away once qrap-less usage is
> established, so just accept EACCES as indication that a conflicting
> socket does not, in fact, exist.

That's reasonable, in addition, another case that would give EACCES is
if some other user has a passt instance running there, in which case
this is still probably the right thing to do.

> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

> ---
>  tap.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/tap.c b/tap.c
> index 4dcff4f..0a3ccce 100644
> --- a/tap.c
> +++ b/tap.c
> @@ -912,7 +912,8 @@ static void tap_sock_unix_init(struct ctx *c)
>  		}
>  
>  		ret = connect(ex, (const struct sockaddr *)&addr, sizeof(addr));
> -		if (!ret || (errno != ENOENT && errno != ECONNREFUSED)) {
> +		if (!ret || (errno != ENOENT && errno != ECONNREFUSED &&
> +			     errno != EACCES)) {
>  			if (*c->sock_path) {
>  				err("Socket path %s already in use", path);
>  				exit(EXIT_FAILURE);

-- 
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 --]

  reply	other threads:[~2022-11-01  0:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 11:20 [PATCH v2 0/5] Test cases to display memory usage in kernel and userspace Stefano Brivio
2022-10-31 11:20 ` [PATCH v2 1/5] test/lib: Move screen-scraping setup and layout functions to _ugly files Stefano Brivio
2022-11-01  0:39   ` David Gibson
2022-10-31 11:20 ` [PATCH v2 2/5] tap: Support for detection of existing sockets on ramfs Stefano Brivio
2022-11-01  0:41   ` David Gibson [this message]
2022-10-31 11:20 ` [PATCH v2 3/5] test/lib/perf_report: Use own flag to track initialisation Stefano Brivio
2022-11-01  0:41   ` David Gibson
2022-10-31 11:20 ` [PATCH v2 4/5] test/lib: Add "td" directive, handled by table_value() Stefano Brivio
2022-11-01  0:42   ` David Gibson
2022-10-31 11:20 ` [PATCH v2 5/5] test: Add memory/passt test cases Stefano Brivio
2022-11-01  0:58   ` David Gibson
2022-11-01  7:59     ` 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=Y2BrKND+LQfs3EAv@yekko \
    --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).