From: Jakub Kicinski <kuba@kernel.org>
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Willem de Bruijn <willemb@google.com>,
kernel-team@cloudflare.com,
syzbot+e15b7e15b8a751a91d9a@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2 0/2] Silence bad offload warning when sending UDP GSO with IPv6 extension headers
Date: Thu, 1 Aug 2024 18:36:59 -0700 [thread overview]
Message-ID: <20240801183659.17c25cbd@kernel.org> (raw)
In-Reply-To: <20240801-udp-gso-egress-from-tunnel-v2-0-9a2af2f15d8d@cloudflare.com>
On Thu, 01 Aug 2024 15:52:52 +0200 Jakub Sitnicki wrote:
> This series addresses a recent regression report from syzbot [1].
> Please see patch 1 description for details.
The test doesn't seem super happy in netdev CI:
https://netdev-3.bots.linux.dev/vmksft-net-dbg/results/709100/79-udpgso-sh/stdout
https://netdev-3.bots.linux.dev/vmksft-net/results/709101/78-udpgso-sh/stdout
https://netdev-3.bots.linux.dev/vmksft-net-dbg/results/708921/75-udpgso-sh/stdout
https://netdev-3.bots.linux.dev/vmksft-net/results/708921/78-udpgso-sh/stdout
next prev parent reply other threads:[~2024-08-02 1:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 13:52 [PATCH net v2 0/2] Silence bad offload warning when sending UDP GSO with IPv6 extension headers Jakub Sitnicki
2024-08-01 13:52 ` [PATCH net v2 1/2] gso: Skip bad offload detection when device supports requested GSO Jakub Sitnicki
2024-08-01 19:13 ` Willem de Bruijn
2024-08-05 10:04 ` Jakub Sitnicki
2024-08-05 14:25 ` Willem de Bruijn
2024-08-05 15:59 ` Jakub Sitnicki
2024-08-05 16:11 ` Willem de Bruijn
2024-08-01 13:52 ` [PATCH net v2 2/2] selftests/net: Add coverage for UDP GSO with IPv6 extension headers Jakub Sitnicki
2024-08-01 19:16 ` Willem de Bruijn
2024-08-08 2:33 ` Willem de Bruijn
2024-08-02 1:36 ` Jakub Kicinski [this message]
2024-08-02 11:20 ` [PATCH net v2 0/2] Silence bad offload warning when sending " Jakub Sitnicki
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=20240801183659.17c25cbd@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+e15b7e15b8a751a91d9a@syzkaller.appspotmail.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 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 NNTP newsgroup(s).