From: patchwork-bot+netdevbpf@kernel•org
To: Nikolay Aleksandrov <razor@blackwall•org>
Cc: netdev@vger•kernel.org, roopa@nvidia•com, bridge@lists•linux.dev,
davem@davemloft•net, kuba@kernel•org, edumazet@google•com,
pabeni@redhat•com, syzkaller-bugs@googlegroups•com,
syzbot+a63a1f6a062033cf0f40@syzkaller•appspotmail.com
Subject: Re: [PATCH net] net: bridge: xmit: make sure we have at least eth header len bytes
Date: Wed, 15 May 2024 10:50:29 +0000 [thread overview]
Message-ID: <171577022971.14646.4487627386797578993.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240513103419.768040-1-razor@blackwall.org>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft•net>:
On Mon, 13 May 2024 13:34:19 +0300 you wrote:
> syzbot triggered an uninit value[1] error in bridge device's xmit path
> by sending a short (less than ETH_HLEN bytes) skb. To fix it check if
> we can actually pull that amount instead of assuming.
>
> Tested with dropwatch:
> drop at: br_dev_xmit+0xb93/0x12d0 [bridge] (0xffffffffc06739b3)
> origin: software
> timestamp: Mon May 13 11:31:53 2024 778214037 nsec
> protocol: 0x88a8
> length: 2
> original length: 2
> drop reason: PKT_TOO_SMALL
>
> [...]
Here is the summary with links:
- [net] net: bridge: xmit: make sure we have at least eth header len bytes
https://git.kernel.org/netdev/net/c/8bd67ebb50c0
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:[~2024-05-15 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 8:04 [syzbot] [bridge?] KMSAN: uninit-value in br_dev_xmit (2) syzbot
2024-05-13 10:34 ` [PATCH net] net: bridge: xmit: make sure we have at least eth header len bytes Nikolay Aleksandrov
2024-05-15 10:50 ` 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=171577022971.14646.4487627386797578993.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=bridge@lists$(echo .)linux.dev \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=razor@blackwall$(echo .)org \
--cc=roopa@nvidia$(echo .)com \
--cc=syzbot+a63a1f6a062033cf0f40@syzkaller$(echo .)appspotmail.com \
--cc=syzkaller-bugs@googlegroups$(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