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]

Message-ID: <87bkm22y6e.fsf@esperi.org.uk>
Date:   Thu, 09 Feb 2023 23:53:29 +0000
From:   Nick Alcock <nick.alcock@...cle.com>
To:     Luis Chamberlain <mcgrof@...nel.org>
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

[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? My understanding is that
if you are, I can just send the lot as one big series, whereas if you're
not I have to do it as a lot of little series to avoid burdening all the
maintainers who will have to take its pieces.

(To me, taking it all at once seems like a lot less work for
everyone... I'm still Cc:ing maintainers on individual commits affecting
their subsystem though. Seems only polite.)