From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] team: fix header_ops type confusion and add selftest
Date: Tue, 24 Mar 2026 10:40:08 +0000 [thread overview]
Message-ID: <177434880804.612784.10063445209003153905.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260320072139.134249-1-jiayuan.chen@linux.dev>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 20 Mar 2026 15:21:25 +0800 you wrote:
> Hi,
>
> This patch series fixes a panic reported by syzkaller in the team/bond/gre
> stacked non-Ethernet configuration:
> https://syzkaller.appspot.com/bug?extid=3d8bc31c45e11450f24c
>
> The first patch fixes the header_ops type confusion / parse recursion
> context issue in team. The second patch adds a selftest to reproduce the
> reported scenario and prevent regressions in the future.
>
> [...]
Here is the summary with links:
- [net,v3,1/2] team: fix header_ops type confusion with non-Ethernet ports
https://git.kernel.org/netdev/net/c/425000dbf173
- [net,v3,2/2] selftests: team: add non-Ethernet header_ops reproducer
https://git.kernel.org/netdev/net/c/56063823b9f0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-24 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 7:21 [PATCH net v3 0/2] team: fix header_ops type confusion and add selftest Jiayuan Chen
2026-03-20 7:21 ` [PATCH net v3 1/2] team: fix header_ops type confusion with non-Ethernet ports Jiayuan Chen
2026-03-20 7:21 ` [PATCH net v3 2/2] selftests: team: add non-Ethernet header_ops reproducer Jiayuan Chen
2026-03-24 10:40 ` patchwork-bot+netdevbpf [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=177434880804.612784.10063445209003153905.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiayuan.chen@linux.dev \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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