public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Yumei Huang <yuhuang@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	passt-dev@passt.top, lvivier@redhat.com
Subject: Re: [PATCH] tap: Drop frames if no client connected
Date: Mon, 15 Sep 2025 08:13:16 +0200	[thread overview]
Message-ID: <20250915081316.31d31db9@elisabeth> (raw)
In-Reply-To: <CANsz47nXMw8P5pfghkERDNfnxYDjG=R4axsES=7w=+eL=wxP3g@mail.gmail.com>

On Fri, 12 Sep 2025 10:45:30 +0800
Yumei Huang <yuhuang@redhat.com> wrote:

> > On Thu, Sep 11, 2025 at 11:54:25AM +0200, Stefano Brivio wrote:  
> >
> > [...]
> >
> > > - until a while ago, this couldn't happen at all. We were just blocking
> > >   the whole execution as long as the tap / guest / container interface
> > >   wasn't up and running.
> > >
> > >   I wonder when this changed and if it makes sense to go back to the
> > >   previous behaviour. I had just a quick look and I wonder if I
> > >   accidentally broke this in c9b241346569 ("conf, passt, tap: Open
> > >   socket and PID files before switching UID/GID").  
> BTW, I read the commit c9b241346569, it didn't change the behaviour.
> Before this, tap_sock_init() will call tap_sock_unix_init() without
> checking if c->fd_tap.

Sure, it didn't check c->fd_tap, but was it blocking the whole
execution?

I'm not sure, I just know that at some point we were blocking
everything. As David mentioned it's not possible with vhost-user
anyway, so it doesn't matter so much.

-- 
Stefano


  reply	other threads:[~2025-09-15  6:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  8:55 [PATCH] tap: Drop frames if no client connected Yumei Huang
2025-09-11  9:54 ` Stefano Brivio
2025-09-12  2:01   ` David Gibson
2025-09-12  2:45     ` Yumei Huang
2025-09-15  6:13       ` Stefano Brivio [this message]
2025-09-15  6:13     ` 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=20250915081316.31d31db9@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=yuhuang@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).