From: patchwork-bot+netdevbpf@kernel.org
To: Grant Grundler <grundler@chromium.org>
Cc: irusskikh@marvell.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, aashay@google.com, yich@google.com,
enlightened@google.com
Subject: Re: [PATCH 0/4 V2] net: atlantic: more fuzzing fixes
Date: Wed, 11 May 2022 11:30:13 +0000 [thread overview]
Message-ID: <165226861367.11801.13863078014011642254.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220510022826.2388423-1-grundler@chromium.org>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 9 May 2022 19:28:22 -0700 you wrote:
> The Chrome OS fuzzing team posted a "Fuzzing" report for atlantic driver
> in Q4 2021 using Chrome OS v5.4 kernel and "Cable Matters
> Thunderbolt 3 to 10 Gb Ethernet" (b0 version):
> https://docs.google.com/document/d/e/2PACX-1vT4oCGNhhy_AuUqpu6NGnW0N9HF_jxf2kS7raOpOlNRqJNiTHAtjiHRthXYSeXIRTgfeVvsEt0qK9qK/pub
>
> It essentially describes four problems:
> 1) validate rxd_wb->next_desc_ptr before populating buff->next
> 2) "frag[0] not initialized" case in aq_ring_rx_clean()
> 3) limit iterations handling fragments in aq_ring_rx_clean()
> 4) validate hw_head_ in hw_atl_b0_hw_ring_tx_head_update()
>
> [...]
Here is the summary with links:
- [1/4] net: atlantic: fix "frag[0] not initialized"
https://git.kernel.org/netdev/net/c/62e0ae0f4020
- [2/4] net: atlantic: reduce scope of is_rsc_complete
https://git.kernel.org/netdev/net/c/79784d77ebbd
- [3/4] net: atlantic: add check for MAX_SKB_FRAGS
https://git.kernel.org/netdev/net/c/6aecbba12b5c
- [4/4] net: atlantic: verify hw_head_ lies within TX buffer ring
https://git.kernel.org/netdev/net/c/2120b7f4d128
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-05-11 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 2:28 Grant Grundler
2022-05-10 2:28 ` [PATCH 1/4] net: atlantic: fix "frag[0] not initialized" Grant Grundler
2022-05-10 2:28 ` [PATCH 2/4] net: atlantic: reduce scope of is_rsc_complete Grant Grundler
2022-05-10 2:28 ` [PATCH 3/4] net: atlantic: add check for MAX_SKB_FRAGS Grant Grundler
2022-05-10 2:28 ` [PATCH 4/4] net: atlantic: verify hw_head_ lies within TX buffer ring Grant Grundler
2022-05-11 11:30 ` 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=165226861367.11801.13863078014011642254.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aashay@google.com \
--cc=davem@davemloft.net \
--cc=enlightened@google.com \
--cc=grundler@chromium.org \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yich@google.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
Powered by JetHome