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: <3158046.1740670591@warthog.procyon.org.uk>
Date: Thu, 27 Feb 2025 15:36:31 +0000
From: David Howells <dhowells@...hat.com>
To: Paolo Abeni <pabeni@...hat.com>
Cc: dhowells@...hat.com, netdev@...r.kernel.org,
    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>,
    Herbert Xu <herbert@...dor.apana.org.au>,
    linux-afs@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Which tree to push afs + crypto + rxrpc spanning patches through?

Paolo Abeni <pabeni@...hat.com> wrote:

> >> The remaining patches in this series touch only AFS, I'm unsure if net-next
> >> if the best target here???
> > 
> > Yeah.  It's tricky as the complete set of patches I would like to post spans
> > three subsystems.
> 
> Possibly sharing a stable tree somewhere, and let the relevant subsystem
> pull the tree specific deps/bits could help?

The networking tree would still have to take the afs and crypto bits in order
to take the rxrpc bits so that the code compiles.  Unfortunately, the rxrpc
bits depend on the other two.

If you're okay with the rxrpc bits not going through the networking tree and
if Herbert is okay with the krb5 library not going through the crypto tree, I
can try pushing the whole lot through the filesystem tree.

David


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ