From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 0/3] More caution with NONBLOCK flag on Unix sockets
Date: Wed, 20 May 2026 02:52:19 +0200 (CEST) [thread overview]
Message-ID: <20260520025219.4dff8d24@elisabeth> (raw)
In-Reply-To: <20260518032243.823768-1-david@gibson.dropbear.id.au>
On Mon, 18 May 2026 13:22:40 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> This is a revision of the one patch from my pesto series that wasn't
> merged: a rework to the handling of the blocking flag for both
> listening and accepted Unix sockets. This new version is split into
> several pieces to make the rationales clearer at each step. It's also
> a bit more cautious in what it does, so should avoid the problems with
> the original version.
>
> David Gibson (3):
> treewide: Add SOCK_CLOEXEC to accept() calls that are missing it
> tap: Report accept() errors
> conf, repair, tap: Document reasons for blocking Unix sockets
Applied, with the nit I reported on 3/3 fixed up.
--
Stefano
prev parent reply other threads:[~2026-05-20 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 3:22 David Gibson
2026-05-18 3:22 ` [PATCH v2 1/3] treewide: Add SOCK_CLOEXEC to accept() calls that are missing it David Gibson
2026-05-18 3:22 ` [PATCH v2 2/3] tap: Report accept() errors David Gibson
2026-05-18 3:22 ` [PATCH v2 3/3] conf, repair, tap: Document reasons for blocking Unix sockets David Gibson
2026-05-20 0:52 ` Stefano Brivio
2026-05-20 1:13 ` David Gibson
2026-05-20 0:52 ` Stefano Brivio [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=20260520025219.4dff8d24@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).