linux-kernel - Re: [PATCH modules-next v10 00/13] kallsyms: reliable symbol->address lookup with /proc/kallmodsyms

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]

Date:   Tue, 21 Feb 2023 13:48:34 -0800
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Nick Alcock <nick.alcock@...cle.com>
Cc:     linux-modules@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
        linux-kernel@...r.kernel.org, elena.zannoni@...cle.com
Subject: Re: [PATCH modules-next v10 00/13] kallsyms: reliable
 symbol->address lookup with /proc/kallmodsyms

On Thu, Feb 09, 2023 at 11:53:29PM +0000, Nick Alcock wrote:
> [most people trimmed from the Cc: list for this procedural question]
> 
> On 9 Feb 2023, Nick Alcock outgrape:
> > I am going to split this whole series into:
> >
> > 1. A series of patches (123 of them at present) Cc:ed to subsystem
> > maintainers as well as you, to comment out the MODULE_LICENSE usage.
> > These patches will have Suggested-by you. This series is rebased against
> > the latest modules-next and revalidated, and is ready to be mailed out;
> > will do so shortly.
> 
> One quick question: if/when you're happy with this series, are you
> planning to take it yourself via modules-next?

It seems some maintainers are already taking patches in, so let's see
what folks take in, then if there are not takers I can just take what is
not merged on linux-next through modules-next.

So try to get them into each subsystem tree, and around rc3 send the
ones that are not merged and I'll just take them into modules-next.

  Luis