From: Greg KH <gregkh@linuxfoundation.org>
To: zhoumin <teczm@foxmail.com>
Cc: rafael@kernel.org, dakr@kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kobject_uevent: add uevent_helper exist check
Date: Mon, 7 Apr 2025 09:00:35 +0200 [thread overview]
Message-ID: <2025040731-eternity-statutory-4a80@gregkh> (raw)
In-Reply-To: <tencent_B971903B40AFCF5878B6532261672A5D6A0A@qq.com>
On Sat, Apr 05, 2025 at 01:31:02AM +0800, zhoumin wrote:
> The kernel creates uevent_helper process for every uevent sent,
> even if the uevent_helper does not exist. Before the rootfs is
> mounted, a large number of events are generated. This change
> introduces uevent_helper existence check to prevent unnecessary
> operations.
What problem is this causing? What changed to make this actually be a
problem?
> Logs a debug messase before call_usermodehelper_setup.
I can not parse this sentence, sorry.
> e.g.: pr_emerg("action:%s devpath:%s\n", action_string, devpath);
> You will see a large number of uevent_helper processes
> are attempted to be created before the rootfs is mounted.
Again, why is that a problem?
> Signed-off-by: zhoumin <teczm@foxmail.com>
Please use your name here, not an alias.
> ---
> lib/kobject_uevent.c | 20 +++++++++++++++++++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
>
> diff --git a/lib/kobject_uevent.c b/lib/kobject_uevent.c
> index b7f2fa08d9c8..f3d34ded141a 100644
> --- a/lib/kobject_uevent.c
> +++ b/lib/kobject_uevent.c
> @@ -28,6 +28,7 @@
> #include <net/sock.h>
> #include <net/netlink.h>
> #include <net/net_namespace.h>
> +#include <linux/namei.h>
>
>
> atomic64_t uevent_seqnum;
> @@ -58,6 +59,23 @@ static const char *kobject_actions[] = {
> [KOBJ_UNBIND] = "unbind",
> };
>
> +#ifdef CONFIG_UEVENT_HELPER
> +static int uevent_helper_lookup(void)
> +{
> + static int ret = -ENOENT;
> + struct path path;
> +
> + if (!ret)
> + return ret;
> +
> + ret = kern_path(uevent_helper, LOOKUP_FOLLOW, &path);
> + if (!ret)
> + path_put(&path);
What happens when the root filesystem changes to the new one? This
feels wrong as Andrew said.
thanks,
greg k-h
next prev parent reply other threads:[~2025-04-07 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 17:31 [PATCH] kobject_uevent: add uevent_helper exist check zhoumin
2025-04-05 22:52 ` Andrew Morton
2025-04-06 6:19 ` zhoumin
2025-04-07 7:01 ` Greg KH
2025-04-07 7:00 ` Greg KH [this message]
2025-04-07 15:18 ` zhoumin
2025-04-07 15:35 ` Greg KH
2025-04-07 16:22 ` zhoumin
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=2025040731-eternity-statutory-4a80@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dakr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=teczm@foxmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.