From: patchwork-bot+netdevbpf@kernel.org
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, caoruide123@gmail.com,
stable@vger.kernel.org, yifanwucs@gmail.com,
tomapufckgml@gmail.com, yuantan098@gmail.com, bird@lzu.edu.cn,
enjou1224z@gmail.com, n05ec@lzu.edu.cn, sven@narfation.org
Subject: Re: [PATCH net 1/2] batman-adv: reject oversized global TT response buffers
Date: Thu, 09 Apr 2026 02:00:23 +0000 [thread overview]
Message-ID: <177570002357.953143.3280189136454174077.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408110255.976389-2-sw@simonwunderlich.de>
Hello:
This series was applied to netdev/net.git (main)
by Simon Wunderlich <sw@simonwunderlich.de>:
On Wed, 8 Apr 2026 13:02:54 +0200 you wrote:
> From: Ruide Cao <caoruide123@gmail.com>
>
> batadv_tt_prepare_tvlv_global_data() builds the allocation length for a
> global TT response in 16-bit temporaries. When a remote originator
> advertises a large enough global TT, the TT payload length plus the VLAN
> header offset can exceed 65535 and wrap before kmalloc().
>
> [...]
Here is the summary with links:
- [net,1/2] batman-adv: reject oversized global TT response buffers
https://git.kernel.org/netdev/net/c/3a359bf5c61d
- [net,2/2] batman-adv: hold claim backbone gateways by reference
https://git.kernel.org/netdev/net/c/82d8701b2c93
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:[~2026-04-09 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260408110255.976389-1-sw@simonwunderlich.de>
2026-04-08 11:02 ` [PATCH net 1/2] batman-adv: reject oversized global TT response buffers Simon Wunderlich
2026-04-09 2:00 ` patchwork-bot+netdevbpf [this message]
2026-04-08 11:02 ` [PATCH net 2/2] batman-adv: hold claim backbone gateways by reference Simon Wunderlich
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=177570002357.953143.3280189136454174077.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=bird@lzu.edu.cn \
--cc=caoruide123@gmail.com \
--cc=davem@davemloft.net \
--cc=enjou1224z@gmail.com \
--cc=kuba@kernel.org \
--cc=n05ec@lzu.edu.cn \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
--cc=tomapufckgml@gmail.com \
--cc=yifanwucs@gmail.com \
--cc=yuantan098@gmail.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