public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/4] Fix possible truncation of frames from /dev/net/tun
Date: Fri, 6 Sep 2024 14:20:04 +0200	[thread overview]
Message-ID: <20240906142004.15775b3f@elisabeth> (raw)
In-Reply-To: <20240906114939.261097-1-david@gibson.dropbear.id.au>

On Fri,  6 Sep 2024 21:49:35 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> These changes started off as part of the series re-introducing EPOLLET
> for tap event handling.  That's now turned out to be of lower
> priority, but along the way we fixed a bug where we could truncate
> frames from the kernel tap interface.
> 
> This is a respin of that patch, plus a few minor preliminary cleanups.
> Various minor tweaks based on feedback from the original posting as
> part of the tap EPOLLET series.
> 
> David Gibson (4):
>   tap: Split out handling of EPOLLIN events
>   tap: Improve handling of EINTR in tap_passt_input()
>   tap: Restructure in tap_pasta_input()
>   tap: Don't risk truncating frames on full buffer in tap_pasta_input()

Applied.

-- 
Stefano


      parent reply	other threads:[~2024-09-06 12:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 11:49 [PATCH 0/4] Fix possible truncation of frames from /dev/net/tun David Gibson
2024-09-06 11:49 ` [PATCH 1/4] tap: Split out handling of EPOLLIN events David Gibson
2024-09-06 11:49 ` [PATCH 2/4] tap: Improve handling of EINTR in tap_passt_input() David Gibson
2024-09-06 11:49 ` [PATCH 3/4] tap: Restructure in tap_pasta_input() David Gibson
2024-09-06 11:49 ` [PATCH 4/4] tap: Don't risk truncating frames on full buffer " David Gibson
2024-09-06 12:20 ` 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=20240906142004.15775b3f@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).