diff options
author | Shyam Saini <shyamsaini@linux.microsoft.com> | 2025-02-27 10:49:30 -0800 |
---|---|---|
committer | Petr Pavlu <petr.pavlu@suse.com> | 2025-04-16 15:10:55 +0200 |
commit | f95bbfe18512c5c018720468959edac056a17196 (patch) | |
tree | 62a3f067bd9ca8084eb154f620fa612ad5d9b259 /scripts/generate_rust_analyzer.py | |
parent | 7c76c813cfc42a7376378a0c4b7250db2eebab81 (diff) | |
download | linux-f95bbfe18512c5c018720468959edac056a17196.tar.gz linux-f95bbfe18512c5c018720468959edac056a17196.tar.bz2 linux-f95bbfe18512c5c018720468959edac056a17196.zip |
drivers: base: handle module_kobject creation
module_add_driver() relies on module_kset list for
/sys/module/<built-in-module>/drivers directory creation.
Since,
commit 96a1a2412acba ("kernel/params.c: defer most of param_sysfs_init() to late_initcall time")
drivers which are initialized from subsys_initcall() or any other
higher precedence initcall couldn't find the related kobject entry
in the module_kset list because module_kset is not fully populated
by the time module_add_driver() refers it. As a consequence,
module_add_driver() returns early without calling make_driver_name().
Therefore, /sys/module/<built-in-module>/drivers is never created.
Fix this issue by letting module_add_driver() handle module_kobject
creation itself.
Fixes: 96a1a2412acb ("kernel/params.c: defer most of param_sysfs_init() to late_initcall time")
Cc: stable@vger.kernel.org # requires all other patches from the series
Suggested-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Signed-off-by: Shyam Saini <shyamsaini@linux.microsoft.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Link: https://lore.kernel.org/r/20250227184930.34163-5-shyamsaini@linux.microsoft.com
Signed-off-by: Petr Pavlu <petr.pavlu@suse.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions