From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/2] Avoid overlapping mempcy() in DUP_ACK handling
Date: Thu, 12 Sep 2024 09:54:06 +0200 [thread overview]
Message-ID: <20240912095406.0448afc5@elisabeth> (raw)
In-Reply-To: <20240912065940.1738239-1-david@gibson.dropbear.id.au>
On Thu, 12 Sep 2024 16:59:38 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> Spotted this so-far harmless, but technically undefined behaviour
> while looking at other things. Fixed one other nit at the same time.
>
> David Gibson (2):
> tcp: Remove redundant initialisation of iov[TCP_IOV_ETH].iov_base
> tcp: Avoid overlapping memcpy() in DUP_ACK handling
>
> tcp_buf.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
Applied.
--
Stefano
prev parent reply other threads:[~2024-09-12 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 6:59 [PATCH 0/2] Avoid overlapping mempcy() in DUP_ACK handling David Gibson
2024-09-12 6:59 ` [PATCH 1/2] tcp: Remove redundant initialisation of iov[TCP_IOV_ETH].iov_base David Gibson
2024-09-12 6:59 ` [PATCH 2/2] tcp: Avoid overlapping memcpy() in DUP_ACK handling David Gibson
2024-09-12 7:54 ` 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=20240912095406.0448afc5@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).