From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Shyam Saini <shyamsaini@linux.microsoft.com>
Cc: linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
code@tyhicks.com, linux@rasmusvillemoes.dk,
christophe.leroy@csgroup.eu, hch@infradead.org,
mcgrof@kernel.org, frkaya@linux.microsoft.com,
vijayb@linux.microsoft.com, petr.pavlu@suse.com,
samitolvanen@google.com, da.gomez@samsung.com,
gregkh@linuxfoundation.org, rafael@kernel.org, dakr@kernel.org
Subject: Re: [v2 2/3] kernel: refactor and globalize lookup_or_create_module_kobject()
Date: Fri, 7 Feb 2025 08:35:28 +0100 [thread overview]
Message-ID: <307ec0eb-df8e-4031-9bfa-227b1cd2fcb7@t-8ch.de> (raw)
In-Reply-To: <20250207054538.1110340-3-shyamsaini@linux.microsoft.com>
On 2025-02-06 21:45:37-0800, Shyam Saini wrote:
> lookup_or_create_module_kobject() is static and marked as __init,
> this is not ideal for global usage.
FYI missing "PATCH" in patch subject.
> Fix this limitation by refactoring and declaring this as global:
> - Refactor it by removing BUG_ON() and 'if else' construct by returning
> early
This does look like an unrelated change, could be in its own patch.
> - Remove static and __init markers from the function and add its
> declaration in module.h
> - Mark this function as "__modinit". To facilitate this, move the
> __modinit macro construct to module.h
>
> Suggested-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
> Signed-off-by: Shyam Saini <shyamsaini@linux.microsoft.com>
> ---
> include/linux/module.h | 8 +++++++
> kernel/params.c | 48 ++++++++++++++++++------------------------
> 2 files changed, 29 insertions(+), 27 deletions(-)
>
> diff --git a/include/linux/module.h b/include/linux/module.h
> index 12f8a7d4fc1c..57d09b4e4385 100644
> --- a/include/linux/module.h
> +++ b/include/linux/module.h
> @@ -162,6 +162,14 @@ extern void cleanup_module(void);
> #define __INITRODATA_OR_MODULE __INITRODATA
> #endif /*CONFIG_MODULES*/
>
> +#ifdef CONFIG_MODULES
> +#define __modinit
> +#else
> +#define __modinit __init
> +#endif
> +
> +struct module_kobject __modinit * lookup_or_create_module_kobject(const char *name);
__init / __modinit is not necessary on the declaration.
You can remove it here and keep the #define private.
> +
> /* Generic info of form tag = "info" */
> #define MODULE_INFO(tag, info) __MODULE_INFO(tag, tag, info)
>
> diff --git a/kernel/params.c b/kernel/params.c
> index 4b43baaf7c83..5d16696b1daa 100644
> --- a/kernel/params.c
> +++ b/kernel/params.c
> @@ -595,12 +595,6 @@ static ssize_t param_attr_store(const struct module_attribute *mattr,
> }
> #endif
>
> -#ifdef CONFIG_MODULES
> -#define __modinit
> -#else
> -#define __modinit __init
> -#endif
> -
> #ifdef CONFIG_SYSFS
> void kernel_param_lock(struct module *mod)
> {
> @@ -763,38 +757,38 @@ void destroy_params(const struct kernel_param *params, unsigned num)
> params[i].ops->free(params[i].arg);
> }
>
> -static struct module_kobject * __init lookup_or_create_module_kobject(const char *name)
> +struct module_kobject __modinit * lookup_or_create_module_kobject(const char *name)
> {
> struct module_kobject *mk;
> struct kobject *kobj;
> int err;
>
> kobj = kset_find_obj(module_kset, name);
> - if (kobj) {
> - mk = to_module_kobject(kobj);
> - } else {
> - mk = kzalloc(sizeof(struct module_kobject), GFP_KERNEL);
> - BUG_ON(!mk);
> -
> - mk->mod = THIS_MODULE;
> - mk->kobj.kset = module_kset;
> - err = kobject_init_and_add(&mk->kobj, &module_ktype, NULL,
> + if (kobj)
> + return to_module_kobject(kobj);
> +
> + mk = kzalloc(sizeof(struct module_kobject), GFP_KERNEL);
> + if (!mk)
> + return NULL;
> +
> + mk->mod = THIS_MODULE;
> + mk->kobj.kset = module_kset;
> + err = kobject_init_and_add(&mk->kobj, &module_ktype, NULL,
> "%s", name);
> #ifdef CONFIG_MODULES
As you are cleaning this up anyways: The #ifdef above should become
if (IS_ENABLED(CONFIG_MODULES))
> - if (!err)
> - err = sysfs_create_file(&mk->kobj, &module_uevent.attr);
> + if (!err)
> + err = sysfs_create_file(&mk->kobj, &module_uevent.attr);
> #endif
> - if (err) {
> - kobject_put(&mk->kobj);
> - pr_crit("Adding module '%s' to sysfs failed (%d), the system may be unstable.\n",
> - name, err);
> - return NULL;
> - }
> -
> - /* So that we hold reference in both cases. */
> - kobject_get(&mk->kobj);
> + if (err) {
> + kobject_put(&mk->kobj);
> + pr_crit("Adding module '%s' to sysfs failed (%d), the system may be unstable.\n",
> + name, err);
> + return NULL;
> }
>
> + /* So that we hold reference in both cases. */
> + kobject_get(&mk->kobj);
> +
> return mk;
> }
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-02-07 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 5:45 [v2 0/3] Properly handle module_kobject creation Shyam Saini
2025-02-07 5:45 ` [v2 1/3] kernel: param: rename locate_module_kobject Shyam Saini
2025-02-07 5:45 ` [v2 2/3] kernel: refactor and globalize lookup_or_create_module_kobject() Shyam Saini
2025-02-07 7:35 ` Thomas Weißschuh [this message]
2025-02-07 9:23 ` Rasmus Villemoes
2025-02-07 5:45 ` [v2 3/3] drivers: base: handle module_kobject creation Shyam Saini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=307ec0eb-df8e-4031-9bfa-227b1cd2fcb7@t-8ch.de \
--to=linux@weissschuh.net \
--cc=christophe.leroy@csgroup.eu \
--cc=code@tyhicks.com \
--cc=da.gomez@samsung.com \
--cc=dakr@kernel.org \
--cc=frkaya@linux.microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rafael@kernel.org \
--cc=samitolvanen@google.com \
--cc=shyamsaini@linux.microsoft.com \
--cc=vijayb@linux.microsoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox