From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 0/5] Handle error events on UDP sockets
Date: Wed, 17 Jul 2024 08:32:17 +0200 [thread overview]
Message-ID: <20240717083217.2340afb8@elisabeth> (raw)
In-Reply-To: <20240717003604.1577052-1-david@gibson.dropbear.id.au>
On Wed, 17 Jul 2024 10:35:59 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> Add handling of the error queue for UDP sockets. We certainly need
> this for the flow table: this is the cause of the epoll loop that
> Stefano noticed. Even without the flow table it should improve
> robustness and debugability.
>
> Along the way we make a few other clean ups.
>
> Changes from v1:
> * Assorted minor changes based on Stefano's review
>
> David Gibson (5):
> conf: Don't configure port forwarding for a disabled protocol
> udp: Make udp_sock_recv static
> udp, tcp: Tweak handling of no_udp and no_tcp flags
> util: Add AF_UNSPEC support to sockaddr_ntop()
> udp: Handle errors on UDP sockets
Applied.
--
Stefano
prev parent reply other threads:[~2024-07-17 6:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 0:35 [PATCH v2 0/5] Handle error events on UDP sockets David Gibson
2024-07-17 0:36 ` [PATCH v2 1/5] conf: Don't configure port forwarding for a disabled protocol David Gibson
2024-07-17 0:36 ` [PATCH v2 2/5] udp: Make udp_sock_recv static David Gibson
2024-07-17 0:36 ` [PATCH v2 3/5] udp, tcp: Tweak handling of no_udp and no_tcp flags David Gibson
2024-07-17 0:36 ` [PATCH v2 4/5] util: Add AF_UNSPEC support to sockaddr_ntop() David Gibson
2024-07-17 0:36 ` [PATCH v2 5/5] udp: Handle errors on UDP sockets David Gibson
2024-07-17 6:32 ` 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=20240717083217.2340afb8@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).