From: patchwork-bot+netdevbpf@kernel.org
To: Mashiro Chen <mashiro.chen@mailbox.org>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jreuter@yaina.de, linux-hams@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net 0/2] net: hamradio: fix missing input validation in bpqether and scc
Date: Sun, 12 Apr 2026 20:30:15 +0000 [thread overview]
Message-ID: <177602581512.3400761.5438499340536330676.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260409024927.24397-1-mashiro.chen@mailbox.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 9 Apr 2026 10:49:25 +0800 you wrote:
> This series fixes two missing input validation bugs in the hamradio
> drivers. Both patches were reviewed by Joerg Reuter (hamradio
> maintainer).
>
> v2 changes:
> - bpqether: no code change; add Acked-by: Joerg Reuter
> - scc: drop the upper bound of 4096 per reviewer feedback;
> only enforce the minimum of 16
>
> [...]
Here is the summary with links:
- [v2,net,1/2] net: hamradio: bpqether: validate frame length in bpq_rcv()
https://git.kernel.org/netdev/net/c/6183bd8723a3
- [v2,net,2/2] net: hamradio: scc: validate bufsize in SIOCSCCSMEM ioctl
https://git.kernel.org/netdev/net/c/8263e484d662
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:[~2026-04-12 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 2:49 [PATCH v2 net 0/2] net: hamradio: fix missing input validation in bpqether and scc Mashiro Chen
2026-04-09 2:49 ` [PATCH v2 net 1/2] net: hamradio: bpqether: validate frame length in bpq_rcv() Mashiro Chen
2026-04-09 2:49 ` [PATCH v2 net 2/2] net: hamradio: scc: validate bufsize in SIOCSCCSMEM ioctl Mashiro Chen
2026-04-09 19:27 ` Joerg Reuter
2026-04-12 20: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=177602581512.3400761.5438499340536330676.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jreuter@yaina.de \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mashiro.chen@mailbox.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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