From: patchwork-bot+netdevbpf@kernel.org
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, liuhangbin@gmail.com,
willemb@google.com, baruch@tkos.co.il, pablo@netfilter.org,
yajun.deng@linux.dev, weiyongjun1@huawei.com,
yuehaibing@huawei.com
Subject: Re: [PATCH net-next] net/af_packet: check len when min_header_len equals to 0
Date: Fri, 29 Jul 2022 11:20:14 +0000 [thread overview]
Message-ID: <165909361470.23060.13320367674986515693.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220727093312.125116-1-shaozhengchao@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 27 Jul 2022 17:33:12 +0800 you wrote:
> User can use AF_PACKET socket to send packets with the length of 0.
> When min_header_len equals to 0, packet_snd will call __dev_queue_xmit
> to send packets, and sock->type can be any type.
>
> Reported-by: syzbot+5ea725c25d06fb9114c4@syzkaller.appspotmail.com
> Fixes: fd1894224407 ("bpf: Don't redirect packets with invalid pkt_len")
> Signed-off-by: Zhengchao Shao <shaozhengchao@huawei.com>
>
> [...]
Here is the summary with links:
- [net-next] net/af_packet: check len when min_header_len equals to 0
https://git.kernel.org/netdev/net-next/c/dc633700f00f
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-07-29 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 9:33 [PATCH net-next] net/af_packet: check len when min_header_len equals to 0 Zhengchao Shao
2022-07-29 11:20 ` 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=165909361470.23060.13320367674986515693.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=baruch@tkos.co.il \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=shaozhengchao@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=willemb@google.com \
--cc=yajun.deng@linux.dev \
--cc=yuehaibing@huawei.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;
as well as URLs for NNTP newsgroup(s).