netdev - Re: [PATCH net-next 00/15] afs, rxrpc: Clean up refcounting on afs_cell and afs

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250227164918.3b05d94e@kernel.org>
Date: Thu, 27 Feb 2025 16:49:18 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: patchwork-bot+netdevbpf@...nel.org
Cc: David Howells <dhowells@...hat.com>, netdev@...r.kernel.org,
 marc.dionne@...istor.com, davem@...emloft.net, edumazet@...gle.com,
 pabeni@...hat.com, brauner@...nel.org, linux-afs@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 00/15] afs, rxrpc: Clean up refcounting on
 afs_cell and afs_server records

On Thu, 27 Feb 2025 19:20:57 +0000 patchwork-bot+netdevbpf@...nel.org
wrote:
> Here is the summary with links:
>   - [net-next,01/15] rxrpc: rxperf: Fix missing decoding of terminal magic cookie
>     https://git.kernel.org/netdev/net-next/c/c34d999ca314
>   - [net-next,02/15] rxrpc: peer->mtu_lock is redundant
>     https://git.kernel.org/netdev/net-next/c/833fefa07444
>   - [net-next,03/15] rxrpc: Fix locking issues with the peer record hash
>     https://git.kernel.org/netdev/net-next/c/71f5409176f4
>   - [net-next,04/15] afs: Fix the server_list to unuse a displaced server rather than putting it
>     https://git.kernel.org/netdev/net-next/c/add117e48df4
>   - [net-next,05/15] afs: Give an afs_server object a ref on the afs_cell object it points to
>     https://git.kernel.org/netdev/net-next/c/1f0fc3374f33

Nice job pw-bot! Turns out the first 5 patches were already in the net
tree with fixes, and now they made their way to Linus. So let's discard
those from v2. And even less of a reason for this to go via networking
:(