From: patchwork-bot+netdevbpf@kernel•org
To: Zhengchao Shao <shaozhengchao@huawei•com>
Cc: bpf@vger•kernel.org, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
hawk@kernel•org, ast@kernel•org, daniel@iogearbox•net,
andrii@kernel•org, martin.lau@linux•dev, song@kernel•org,
yhs@fb•com, john.fastabend@gmail•com, kpsingh@kernel•org,
sdf@google•com, bigeasy@linutronix•de, imagedong@tencent•com,
petrm@nvidia•com, arnd@arndb•de, dsahern@kernel•org,
talalahmad@google•com, keescook@chromium•org, haoluo@google•com,
jolsa@kernel•org, weiyongjun1@huawei•com, yuehaibing@huawei•com
Subject: Re: [PATCH v4,bpf-next] bpf: Don't redirect packets with invalid pkt_len
Date: Tue, 19 Jul 2022 17:00:14 +0000 [thread overview]
Message-ID: <165825001414.21239.5976197980941265711.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220715115559.139691-1-shaozhengchao@huawei.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel•org>:
On Fri, 15 Jul 2022 19:55:59 +0800 you wrote:
> Syzbot found an issue [1]: fq_codel_drop() try to drop a flow whitout any
> skbs, that is, the flow->head is null.
> The root cause, as the [2] says, is because that bpf_prog_test_run_skb()
> run a bpf prog which redirects empty skbs.
> So we should determine whether the length of the packet modified by bpf
> prog or others like bpf_prog_test is valid before forwarding it directly.
>
> [...]
Here is the summary with links:
- [v4,bpf-next] bpf: Don't redirect packets with invalid pkt_len
https://git.kernel.org/bpf/bpf-next/c/fd1894224407
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-07-19 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 11:55 [PATCH v4,bpf-next] bpf: Don't redirect packets with invalid pkt_len Zhengchao Shao
2022-07-15 23:30 ` Stanislav Fomichev
2022-07-19 17:00 ` patchwork-bot+netdevbpf [this message]
2022-11-03 21:07 ` Martin KaFai Lau
2022-11-03 21:36 ` Stanislav Fomichev
2022-11-03 22:42 ` Martin KaFai Lau
2022-11-03 22:58 ` Stanislav Fomichev
2022-11-09 21:43 ` Stanislav Fomichev
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=165825001414.21239.5976197980941265711.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrii@kernel$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=ast@kernel$(echo .)org \
--cc=bigeasy@linutronix$(echo .)de \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=haoluo@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=imagedong@tencent$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=keescook@chromium$(echo .)org \
--cc=kpsingh@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=martin.lau@linux$(echo .)dev \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=petrm@nvidia$(echo .)com \
--cc=sdf@google$(echo .)com \
--cc=shaozhengchao@huawei$(echo .)com \
--cc=song@kernel$(echo .)org \
--cc=talalahmad@google$(echo .)com \
--cc=weiyongjun1@huawei$(echo .)com \
--cc=yhs@fb$(echo .)com \
--cc=yuehaibing@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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