From: patchwork-bot+netdevbpf@kernel.org
To: Marek Czernohous <mczernohous@gmail.com>
Cc: netdev@vger.kernel.org, rain.1986.08.12@gmail.com,
zyjzyj2000@gmail.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
tobiasdiedrich@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] forcedeth: two register-window bounds fixes
Date: Thu, 20 Aug 2026 19:30:36 +0000 [thread overview]
Message-ID: <178725423663.446762.8387913060215636639.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <178682367884.3748309.5288746298966501007@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 15 Aug 2026 21:54:38 +0200 you wrote:
> From: Marek Czernohous <marek@czernohous.de>
>
> Two bounds fixes in forcedeth, both in the same shape: a loop that walks
> the register window one step too far. They are independent of each other
> and touch different functions.
>
> 1/2 nv_suspend() and nv_resume() save and restore the non-PCI config
> space with i <= register_size/sizeof(u32). On a VER3 device that is
> exactly the length of saved_config_space[], so the last iteration
> reads and writes one element past the array, and on resume it
> writel()s that element one dword past the length the driver mapped.
> UBSAN catches it.
>
> [...]
Here is the summary with links:
- [net,1/2] forcedeth: fix off-by-one when saving/restoring non-PCI config space
https://git.kernel.org/netdev/net/c/9393f1d656a7
- [net,2/2] forcedeth: stop the tx_timeout register dump past the requested window
https://git.kernel.org/netdev/net/c/cfa9178ce2e5
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-08-20 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 19:54 [PATCH net 0/2] forcedeth: two register-window bounds fixes Marek Czernohous
2026-08-15 19:54 ` [PATCH net 1/2] forcedeth: fix off-by-one when saving/restoring non-PCI config space Marek Czernohous
2026-08-19 8:55 ` Simon Horman
2026-08-19 15:09 ` Zhu Yanjun
2026-08-15 19:54 ` [PATCH net 2/2] forcedeth: stop the tx_timeout register dump past the requested window Marek Czernohous
2026-08-19 8:55 ` Simon Horman
2026-08-19 15:10 ` Zhu Yanjun
2026-08-20 19: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=178725423663.446762.8387913060215636639.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=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mczernohous@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rain.1986.08.12@gmail.com \
--cc=tobiasdiedrich@gmail.com \
--cc=zyjzyj2000@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