linux-kernel - Re: linux-next: manual merge of the keys-next tree with the modules tree

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: <CABCJKuf10mJnunp0gt0r-5Jnumss5LS1VjN51WQmJgnggE+BGA@mail.gmail.com>
Date: Fri, 30 Jan 2026 10:10:34 -0800
From: Sami Tolvanen <samitolvanen@...gle.com>
To: David Howells <dhowells@...hat.com>
Cc: Mark Brown <broonie@...nel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>, Petr Pavlu <petr.pavlu@...e.com>
Subject: Re: linux-next: manual merge of the keys-next tree with the modules tree

On Fri, Jan 30, 2026 at 9:57 AM David Howells <dhowells@...hat.com> wrote:
>
> Sami Tolvanen <samitolvanen@...gle.com> wrote:
>
> > Thanks, Mark. David, I see the patches in keys-next were updated just
> > a few hours ago. Would it make sense for you to rebase them on top of
> > next-20260129? Petr's patch removed the use_signed_attrs variable, so
> > we should ensure it's still initialized correctly. Otherwise the
> > resolution looks trivial.
>
> Wouldn't that mean having to rebase before sending to Linus?

Do you plan to send these to Linus for 7.0-rc1? The patches already
depend on libcrypto-next landing first, right? If the patches were
last rebased 6h ago, I'm not sure if rebasing them on top of
modules-next would significantly affect the linux-next soak time, but
I'm fine either way.

> What's your branch that is being taken into linux-next?

https://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git/log/?h=modules-next

Sami