From: Jakub Kicinski <kuba@kernel.org>
To: John Fastabend <john.fastabend@gmail.com>
Cc: daniel@iogearbox.net, davem@davemloft.net, ast@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [0/1 bpf-next] fix panic bringing up veth with xdp progs
Date: Wed, 9 Nov 2022 18:25:50 -0800 [thread overview]
Message-ID: <20221109182550.4090a6c0@kernel.org> (raw)
In-Reply-To: <20221108221650.808950-1-john.fastabend@gmail.com>
On Tue, 8 Nov 2022 14:16:49 -0800 John Fastabend wrote:
> Not sure if folks want to take this through BPF tree or networking tree.
Whatever's easiest :) FWIW
Acked-by: Jakub Kicinski <kuba@kernel.org>
> 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.
>
> Sorry maintainers resent with CC'ing actual lists. Had a scripting
> issue. Also dropped henqqi has they are bouncing.
Adding Paolo, who had comments on this patch in the past.
The entire concept is worth mainintaining in your opinion, I take it?
next prev parent reply other threads:[~2022-11-10 2:25 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 ` Jakub Kicinski [this message]
2022-11-10 5:10 ` [0/1 bpf-next] fix panic bringing up veth with xdp progs patchwork-bot+netdevbpf
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=20221109182550.4090a6c0@kernel.org \
--to=kuba@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=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.