linux-kernel - Re: [PATCH v2] module: Don't wait for GOING modules

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: <Y5FPkEgEbDlVXkRK@bombadil.infradead.org>
Date:   Wed, 7 Dec 2022 18:44:32 -0800
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Petr Mladek <pmladek@...e.com>
Cc:     Petr Pavlu <petr.pavlu@...e.com>, prarit@...hat.com,
        david@...hat.com, mwilck@...e.com, linux-modules@...r.kernel.org,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v2] module: Don't wait for GOING modules

On Wed, Dec 07, 2022 at 04:15:21PM +0100, Petr Mladek wrote:
> Reviewed-by: Petr Mladek <pmladek@...e.com>

Queued onto modules-next.

> Of course, the ideal solution would be to avoid the multiple
> loads in the first place. AFAIK, everything starts in the kernel
> that sends the same udev events for each CPU...

Fixes go first, *then we can address enhancements. I have some old
fixes I can send after htis is merged. I believe folks have others.

  Luis