linux-kernel - Re: [PATCH v3 0/2] dyndbg: let's use the module notifier callback

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:   Fri, 3 Mar 2023 14:06:27 -0800
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Jason Baron <jbaron@...mai.com>
Cc:     jim.cromie@...il.com, gregkh@...uxfoundation.org,
        linux-kernel@...r.kernel.org, linux-modules@...r.kernel.org
Subject: Re: [PATCH v3 0/2] dyndbg: let's use the module notifier callback

On Fri, Mar 03, 2023 at 11:50:54AM -0500, Jason Baron wrote:
> Hi,
> 
> Jim Cromie hit a BUG() while toggling jump label branches in a module
> before they were properly initialized. This isn't currently an issue,
> but will be as part of his pending classmap series. Seems like we
> should covert to using module callback notifier for dynamic debug
> anyways to match other subsystems and remove core module code.
> First patch is just a cleanup.
> 
> Link: https://lore.kernel.org/lkml/20230113193016.749791-21-jim.cromie@xxxxxxxxx/
> 
> I've rebased this series onto modules-next tree. Although the first patch
> is a cleanup entirely internal to dynamic debug I think it's a nice cleanup
> to have as part of this series.

Thanks! Queued onto modules-next.

  Luis