public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 11/13] passt-repair: Simplify construction of Unix path from inotify
Date: Tue, 21 Apr 2026 12:43:42 +1000	[thread overview]
Message-ID: <20260421024344.1379633-12-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20260421024344.1379633-1-david@gibson.dropbear.id.au>

When passt-repair is invoked with a directory name, it waits for a Unix
socket to appear in that directory.  We need to build the Unix path name
from the given directory, plus the stem file name from the inotify event.

Currently, we build that path into a temporary buffer of size PATH_MAX,
then move it into the smaller buffer inside the Unix sockaddr.  There's no
particular reason for this two step process, we can build the address
directly within the sockaddr_un.  This will give a slightly different error
if the constructed path exceeds the maximum length of a Unix address, but
it will fail either way so it doesn't really matter.

Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
 passt-repair.c | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/passt-repair.c b/passt-repair.c
index 980b0b09..d4c8ce9a 100644
--- a/passt-repair.c
+++ b/passt-repair.c
@@ -64,10 +64,9 @@ static int wait_for_socket(struct sockaddr_un *a, const char *dir,
 	char buf[sizeof(struct inotify_event) + NAME_MAX + 1]
 		__attribute__ ((aligned(__alignof__(struct inotify_event))));
 	const struct inotify_event *ev = NULL;
-	char path[PATH_MAX + 1];
 	bool found = false;
+	int fd, ret;
 	ssize_t n;
-	int fd;
 
 	if ((fd = inotify_init1(IN_CLOEXEC)) < 0) {
 		fprintf(stderr, "inotify_init1: %i\n", errno);
@@ -113,13 +112,15 @@ static int wait_for_socket(struct sockaddr_un *a, const char *dir,
 		_exit(1);
 	}
 
-	snprintf(path, sizeof(path), "%s/%s", dir, ev->name);
-	if ((stat(path, sb))) {
-		fprintf(stderr, "Can't stat() %s: %i\n", path, errno);
+	ret = snprintf(a->sun_path, sizeof(a->sun_path), "%s/%s",
+		       dir, ev->name);
+
+	if ((stat(a->sun_path, sb))) {
+		fprintf(stderr, "Can't stat() %s: %i\n", a->sun_path, errno);
 		_exit(1);
 	}
 
-	return snprintf(a->sun_path, sizeof(a->sun_path), "%s", path);
+	return ret;
 }
 
 /**
-- 
2.53.0


  parent reply	other threads:[~2026-04-21  2:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  2:43 [PATCH 00/13] Improvements to static checker invocation David Gibson
2026-04-21  2:43 ` [PATCH 01/13] Makefile: Use make variables for static checker configuration David Gibson
2026-04-21  2:43 ` [PATCH 02/13] cppcheck: Split out essential defines into a BASE_CPPFLAGS variable David Gibson
2026-04-21  2:43 ` [PATCH 03/13] Makefile: Remove preprocessor flags from $(FLAGS) David Gibson
2026-04-21  2:43 ` [PATCH 04/13] Makefile: Remove non-standard $(FLAGS) variable David Gibson
2026-04-21  2:43 ` [PATCH 05/13] Makefile: Make conditional definition of $(BIN) clearer David Gibson
2026-04-21  2:43 ` [PATCH 06/13] Makefile: Use common binary compilation rule David Gibson
2026-04-21  2:43 ` [PATCH 07/13] Makefile: Remove unhelpful $(HEADERS) variable David Gibson
2026-04-21  2:43 ` [PATCH 08/13] Makefile: Add header dependencies for secondary binaries David Gibson
2026-04-21  2:43 ` [PATCH 09/13] Makefile: Split static checker targets David Gibson
2026-04-21  2:43 ` [PATCH 10/13] passt-repair: Split out inotify handling to its own function David Gibson
2026-04-21  2:43 ` David Gibson [this message]
2026-04-21  2:43 ` [PATCH 12/13] passt-repair: Run static checkers David Gibson
2026-04-21  2:43 ` [PATCH 13/13] qrap: " David Gibson
2026-04-21  3:03 ` [PATCH 00/13] Improvements to static checker invocation 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=20260421024344.1379633-12-david@gibson.dropbear.id.au \
    --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).