linux-kernel - Re: [PATCH 1/1 module-testing] kallsyms: enhance %pS/s/b printing when KALLSYSMS is disabled

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: <YjuZa8Jd2+gpiM3J@bombadil.infradead.org>
Date:   Wed, 23 Mar 2022 15:04:27 -0700
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Maninder Singh <maninder1.s@...sung.com>, akpm@...ux-foundation.org
Cc:     pmladek@...e.com, rostedt@...dmis.org, senozhatsky@...omium.org,
        andriy.shevchenko@...ux.intel.com, linux@...musvillemoes.dk,
        wangkefeng.wang@...wei.com, v.narang@...sung.com,
        swboyd@...omium.org, ojeda@...nel.org,
        linux-kernel@...r.kernel.org, linux-modules@...r.kernel.org,
        avimalin@...il.com, atomlin@...hat.com, keescook@...omium.org,
        ndesaulniers@...gle.com, rdunlap@...radead.org, void@...ifault.com
Subject: Re: [PATCH 1/1 module-testing] kallsyms: enhance %pS/s/b printing
 when KALLSYSMS is disabled

On Wed, Mar 23, 2022 at 10:17:42PM +0530, Maninder Singh wrote:
> ---
> module-next -> module-testing: Petr's review and test tag is picked from previous version,
> current version has slight changes (module.c -> module/main.c). No functional change in patch,
> only init_build_id() function is moved to module/main.c as it can be independent of
> kallsyms.

Andrew,

I see this patch is merged on your tree, any chance we can yield until
the next release and I can then take it under modules-next ? It would
help given the slew of changes I now have queued up not for v5.18 but
for v5.19. I'm delaying the modules changes for v5.19 given the timing,
it is too soon to merge for v5.18 as I want tons of testing on this
all on linux-next after v5.18-rc1 is out.

  Luis