netdev - Re: [PATCH net v2] net/sched: act_mirred: Don't zero blockid when net device is being deleted

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: 
 <170751243027.9207.4165229488561709705.git-patchwork-notify@kernel.org>
Date: Fri, 09 Feb 2024 21:00:30 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Victor Nogueira <victor@...atatu.com>
Cc: jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
 davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 netdev@...r.kernel.org, kernel@...atatu.com, pctammela@...atatu.com
Subject: Re: [PATCH net v2] net/sched: act_mirred: Don't zero blockid when net
 device is being deleted

Hello:

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

On Wed,  7 Feb 2024 19:29:02 -0300 you wrote:
> While testing tdc with parallel tests for mirred to block we caught an
> intermittent bug. The blockid was being zeroed out when a net device
> was deleted and, thus, giving us an incorrect blockid value whenever
> we tried to dump the mirred action. Since we don't increment the block
> refcount in the control path (and only use the ID), we don't need to
> zero the blockid field whenever a net device is going down.
> 
> [...]

Here is the summary with links:
  - [net,v2] net/sched: act_mirred: Don't zero blockid when net device is being deleted
    https://git.kernel.org/netdev/net/c/aae09a6c7783

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