From: Daniel Borkmann <daniel@iogearbox.net>
To: Yan Zhai <yan@cloudflare.com>
Cc: bpf@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Ahern <dsahern@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>, Thomas Graf <tgraf@suug.ch>,
Jordan Griege <jgriege@cloudflare.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 bpf 0/4] lwt: fix return values of BPF ops
Date: Fri, 18 Aug 2023 18:08:34 +0200 [thread overview]
Message-ID: <61e79414-9290-736f-6a50-dfe1585dc2a7@iogearbox.net> (raw)
In-Reply-To: <CAO3-PbqUczUxg42ECStsZnAybYKBY-hJePN=V-JbPvq-BS4cGA@mail.gmail.com>
On 8/18/23 6:01 PM, Yan Zhai wrote:
> On Fri, Aug 18, 2023 at 9:55 AM Daniel Borkmann <daniel@iogearbox.net> wrote:
>>
>> On 8/18/23 4:58 AM, Yan Zhai wrote:
>>> lwt xmit hook does not expect positive return values in function
>>> ip_finish_output2 and ip6_finish_output. However, BPF programs can
>>> directly return positive statuses such like NET_XMIT_DROP, NET_RX_DROP,
>>> and etc to the caller. Such return values would make the kernel continue
>>> processing already freed skbs and eventually panic.
>>>
>>> This set fixes the return values from BPF ops to unexpected continue
>>> processing, checks strictly on the correct continue condition for
>>> future proof. In addition, add missing selftests for BPF redirect
>>> and reroute cases for BPF-CI.
>>>
>>> v5: https://lore.kernel.org/bpf/cover.1692153515.git.yan@cloudflare.com/
>>> v4: https://lore.kernel.org/bpf/ZMD1sFTW8SFiex+x@debian.debian/T/
>>> v3: https://lore.kernel.org/bpf/cover.1690255889.git.yan@cloudflare.com/
>>> v2: https://lore.kernel.org/netdev/ZLdY6JkWRccunvu0@debian.debian/
>>> v1: https://lore.kernel.org/bpf/ZLbYdpWC8zt9EJtq@debian.debian/
>>>
>>> changes since v5:
>>> * fix BPF-CI failures due to missing config and busybox ping issue
>>
>> Series looks good, thanks! Given we're fairly close to merge window and
>> this has been broken for quite some time, I took this into bpf-next.
>>
> Thanks Daniel! Can you also queue this up for stable (or guide how I can do it)?
Given the Fixes tags, it will be picked up automatically once it lands in
Linus' tree.
Thanks,
Daniel
next prev parent reply other threads:[~2023-08-18 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 2:58 Yan Zhai
2023-08-18 2:58 ` [PATCH v6 bpf 1/4] lwt: fix return values of BPF xmit ops Yan Zhai
2023-08-18 2:58 ` [PATCH v6 bpf 2/4] lwt: check LWTUNNEL_XMIT_CONTINUE strictly Yan Zhai
2023-08-18 2:58 ` [PATCH v6 bpf 3/4] selftests/bpf: add lwt_xmit tests for BPF_REDIRECT Yan Zhai
2023-08-18 2:58 ` [PATCH v6 bpf 4/4] selftests/bpf: add lwt_xmit tests for BPF_REROUTE Yan Zhai
2023-08-18 14:55 ` [PATCH v6 bpf 0/4] lwt: fix return values of BPF ops Daniel Borkmann
2023-08-18 16:01 ` Yan Zhai
2023-08-18 16:08 ` Daniel Borkmann [this message]
2023-08-18 16:10 ` Yan Zhai
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=61e79414-9290-736f-6a50-dfe1585dc2a7@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=jgriege@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=tgraf@suug.ch \
--cc=yan@cloudflare.com \
--cc=yhs@fb.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
all inboxes | Powered by JetHome®