From: David Ahern <dsahern@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "Paolo Abeni" <pabeni@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
netdev@vger.kernel.org, "Neal Cardwell" <ncardwell@google.com>,
"Dragos Tatulea" <dtatulea@nvidia.com>,
eric.dumazet@gmail.com, "Maciej Żenczykowski" <maze@google.com>,
"Willem de Bruijn" <willemb@google.com>,
"Shachar Kagan" <skagan@nvidia.com>
Subject: Re: [PATCH net-next 1/2] tcp: conditionally call ip_icmp_error() from tcp_v4_err()
Date: Thu, 18 Apr 2024 11:02:29 -0700 [thread overview]
Message-ID: <44e406a9-e3e7-44c7-9f79-c76280336ca3@kernel.org> (raw)
In-Reply-To: <CANn89iJOLPH72pkqLWm-E4dPKL4yWxTfyJhord0r_cPcRm9WiQ@mail.gmail.com>
On 4/18/24 11:47 AM, Eric Dumazet wrote:
> I think the userspace program relied on a bug added in linux in 2020
which test - when was it added? nettest.c and the fcnal script were
merged in 2019.
next prev parent reply other threads:[~2024-04-18 18:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 16:57 [PATCH net-next 0/2] tcp: tcp_v4_err() changes Eric Dumazet
2024-04-17 16:57 ` [PATCH net-next 1/2] tcp: conditionally call ip_icmp_error() from tcp_v4_err() Eric Dumazet
2024-04-17 17:08 ` Maciej Żenczykowski
2024-04-18 3:22 ` Jason Xing
2024-04-18 6:45 ` Eric Dumazet
2024-04-18 6:53 ` Jason Xing
2024-04-18 8:02 ` Paolo Abeni
2024-04-18 8:03 ` Eric Dumazet
2024-04-18 9:26 ` Eric Dumazet
2024-04-18 9:58 ` Paolo Abeni
2024-04-18 10:15 ` Eric Dumazet
2024-04-18 10:22 ` Eric Dumazet
2024-04-18 10:36 ` Eric Dumazet
2024-04-18 17:46 ` David Ahern
2024-04-18 17:47 ` Eric Dumazet
2024-04-18 18:02 ` David Ahern [this message]
2024-04-18 18:09 ` Eric Dumazet
2024-04-18 18:09 ` Jakub Kicinski
2024-04-18 18:14 ` Eric Dumazet
2024-04-18 20:20 ` David Ahern
2024-04-18 17:56 ` David Ahern
2024-04-17 16:57 ` [PATCH net-next 2/2] tcp: no longer abort SYN_SENT when receiving some ICMP (II) Eric Dumazet
2024-04-18 3:24 ` Jason Xing
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=44e406a9-e3e7-44c7-9f79-c76280336ca3@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=maze@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skagan@nvidia.com \
--cc=willemb@google.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.