From: patchwork-bot+netdevbpf@kernel.org
To: John Fastabend <john.fastabend@gmail.com>
Cc: daniel@iogearbox.net, kuba@kernel.org, davem@davemloft.net,
ast@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [0/1 bpf-next] fix panic bringing up veth with xdp progs
Date: Thu, 10 Nov 2022 05:10:14 +0000 [thread overview]
Message-ID: <166805701452.8788.5070214676768918519.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221108221650.808950-1-john.fastabend@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Tue, 8 Nov 2022 14:16:49 -0800 you wrote:
> Not sure if folks want to take this through BPF tree or networking tree.
> I took a quick look and didn't see any pending fixes so seems no one
> has noticed the panic yet. It reproducible and easy to repro.
>
> I put bpf in the title thinking it woudl be great to run through the
> BPF selftests given its XDP triggering the panic.
>
> [...]
Here is the summary with links:
- [1/1,bpf-next] bpf: veth driver panics when xdp prog attached before veth_open
https://git.kernel.org/bpf/bpf-next/c/5e5dc33d5dac
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:[~2022-11-10 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 22:16 [0/1 bpf-next] fix panic bringing up veth with xdp progs John Fastabend
2022-11-08 22:16 ` [1/1 bpf-next] bpf: veth driver panics when xdp prog attached before veth_open John Fastabend
2022-11-10 2:25 ` [0/1 bpf-next] fix panic bringing up veth with xdp progs Jakub Kicinski
2022-11-10 5:10 ` 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=166805701452.8788.5070214676768918519.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).