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: <899dfc34-bff8-4f41-8c8c-b9aa457880df@redhat.com>
Date: Thu, 27 Feb 2025 12:27:44 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: David Howells <dhowells@...hat.com>, netdev@...r.kernel.org
Cc: Marc Dionne <marc.dionne@...istor.com>, Jakub Kicinski <kuba@...nel.org>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 Christian Brauner <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 2/25/25 12:41 AM, David Howells wrote:
> Here are some patches that fix an occasional hang that's only really
> encountered when rmmod'ing the kafs module.  Arguably, this could also go
> through the vfs tree, but I have a bunch more primarily crypto and rxrpc
> patches that need to go through net-next on top of this[1].
> 
> Now, at the beginning of this set, I've included five fix patches that are
> already committed to the net/main branch but that need to be applied first,
> but haven't made their way into net-next/main or upstream as yet:
> 
>     rxrpc: rxperf: Fix missing decoding of terminal magic cookie
>     rxrpc: peer->mtu_lock is redundant
>     rxrpc: Fix locking issues with the peer record hash
>     afs: Fix the server_list to unuse a displaced server rather than putting it
>     afs: Give an afs_server object a ref on the afs_cell object it points to

You don't need to re-post such patches, just wait a couple of days, when
net will be merged back into net-next. So that we will not have
"duplicate changes" inside the tree.

The remaining patches in this series touch only AFS, I'm unsure if
net-next if the best target here??? The rxrpc follow-up could just wait
the upcoming net -> net-next merge. AFAICS crypto patches go trough
their own tree.

Thanks!

Paolo