netdev - Re: [PATCH net v2] net: gro_cells: Reduce lock scope in gro_cell

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <176239381124.3828781.17654602737481608189.git-patchwork-notify@kernel.org>
Date: Thu, 06 Nov 2025 01:50:11 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: netdev@...r.kernel.org, kuba@...nel.org, edumazet@...gle.com,
 gal@...dia.com, linux-rt-devel@...ts.linux.dev, davem@...emloft.net,
 pabeni@...hat.com, horms@...nel.org, clrkwllms@...nel.org,
 rostedt@...dmis.org
Subject: Re: [PATCH net v2] net: gro_cells: Reduce lock scope in gro_cell_poll

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Tue, 4 Nov 2025 16:34:35 +0100 you wrote:
> One GRO-cell device's NAPI callback can nest into the GRO-cell of
> another device if the underlying device is also using GRO-cell.
> This is the case for IPsec over vxlan.
> These two GRO-cells are separate devices. From lockdep's point of view
> it is the same because each device is sharing the same lock class and so
> it reports a possible deadlock assuming one device is nesting into
> itself.
> 
> [...]

Here is the summary with links:
  - [net,v2] net: gro_cells: Reduce lock scope in gro_cell_poll
    https://git.kernel.org/netdev/net/c/d917c217b612

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html