From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH] passt-repair: Send one confirmation *per command*, not *per socket*
Date: Sat, 8 Feb 2025 10:45:12 +1100 [thread overview]
Message-ID: <Z6abCOB24MEiRz2P@zatzit> (raw)
In-Reply-To: <20250207080358.3491153-1-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2254 bytes --]
On Fri, Feb 07, 2025 at 09:03:58AM +0100, Stefano Brivio wrote:
> It looks like me, myself and I couldn't agree on the "simple" protocol
> between passt and passt-repair. The man page and passt say it's one
> confirmation per command, but the passt-repair implementation had one
> confirmation per socket instead.
>
> This caused all sort of mysterious issues with repair mode
> pseudo-randomly enabled, and leading to hours of fun (mostly not
> mine). Oops.
>
> Switch to one confirmation per command (of course).
>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Ouch.
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> passt-repair.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/passt-repair.c b/passt-repair.c
> index 322066a..614cee0 100644
> --- a/passt-repair.c
> +++ b/passt-repair.c
> @@ -63,6 +63,7 @@ int main(int argc, char **argv)
> struct cmsghdr *cmsg;
> struct msghdr msg;
> struct iovec iov;
> + int op;
>
> prctl(PR_SET_DUMPABLE, 0);
>
> @@ -150,25 +151,24 @@ loop:
> _exit(1);
> }
>
> - for (i = 0; i < n; i++) {
> - int o = cmd;
> + op = cmd;
>
> - if (setsockopt(fds[i], SOL_TCP, TCP_REPAIR, &o, sizeof(o))) {
> + for (i = 0; i < n; i++) {
> + if (setsockopt(fds[i], SOL_TCP, TCP_REPAIR, &op, sizeof(op))) {
> fprintf(stderr,
> - "Setting TCP_REPAIR to %i on socket %i: %s", o,
> + "Setting TCP_REPAIR to %i on socket %i: %s", op,
> fds[i], strerror(errno));
> _exit(1);
> }
>
> /* Close _our_ copy */
> close(fds[i]);
> + }
>
> - /* Confirm setting by echoing the command back */
> - if (send(s, &cmd, sizeof(cmd), 0) < 0) {
> - fprintf(stderr, "Reply to command %i: %s\n",
> - o, strerror(errno));
> - _exit(1);
> - }
> + /* Confirm setting by echoing the command back */
> + if (send(s, &cmd, sizeof(cmd), 0) < 0) {
> + fprintf(stderr, "Reply to %i: %s\n", op, strerror(errno));
> + _exit(1);
> }
>
> goto loop;
--
David Gibson (he or they) | 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 --]
prev parent reply other threads:[~2025-02-07 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 8:03 [PATCH] passt-repair: Send one confirmation *per command*, not *per socket* Stefano Brivio
2025-02-07 23:45 ` David Gibson [this message]
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=Z6abCOB24MEiRz2P@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).