Re: [RFC PATCH 0/2] Decouple ftrace/livepatch from module loader via notifier priority and reverse traversal
Christoph Hellwig <[email protected]>
| Newsgroups | gmane.linux.acpi.devel,gmane.linux.kernel.modules,gmane.linux.kernel,gmane.linux.kernel.clk,gmane.linux.power-management.general,gmane.linux.raid,gmane.linux.kernel.debugging.kgdb.bugs,gmane.linux.network |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Apr 13, 2026 at 04:01:40PM +0800, [email protected] wrote: > From: Song Chen <[email protected]> > > This patchset addresses a long-standing tight coupling between the > module loader and two of its key consumers: ftrace and livepatch. > > Background: > > The module loader currently hard-codes direct calls to > ftrace_module_enable(), klp_module_coming(), klp_module_going() and > ftrace_release_mod() inside prepare_coming_module() and the module > unload path. And that is bad why? > 13 files changed, 290 insertions(+), 74 deletions(-) This is a lot of new complex code touching a lot of places for no obvious gain. What is the reason for this series? Does it prepare for something else?