From: Corey Minyard <corey@minyard.net>
To: Yuho Choi <dbgh9129@gmail.com>
Cc: openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] ipmi: Remove all sysfs files on registration failure
Date: Mon, 3 Aug 2026 10:20:54 -0500 [thread overview]
Message-ID: <anCx1qbu3miWg2lI@mail.minyard.net> (raw)
In-Reply-To: <20260803015550.618808-1-dbgh9129@gmail.com>
On Sun, Aug 02, 2026 at 09:55:50PM -0400, Yuho Choi wrote:
> ipmi_add_smi() creates the nr_users and nr_msgs files before trying to
> create the maintenance_mode file. If that last creation fails, the error
> path removes only nr_users before dropping the final reference to the
> interface.
>
> Remove nr_msgs as well so no sysfs attribute embedded in the freed
> interface remains registered.
Thanks, this is queued for next release.
I've also copied stable for a backport to 6.18.
-corey
>
> Fixes: 627118470fcc ("ipmi: Add a maintenance mode sysfs file")
> Signed-off-by: Yuho Choi <dbgh9129@gmail.com>
> ---
> drivers/char/ipmi/ipmi_msghandler.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c
> index ab4c85f3d6fe..546b7ca8d68e 100644
> --- a/drivers/char/ipmi/ipmi_msghandler.c
> +++ b/drivers/char/ipmi/ipmi_msghandler.c
> @@ -3740,6 +3740,7 @@ int ipmi_add_smi(struct module *owner,
> sysfs_attr_init(&intf->maintenance_mode_devattr.attr);
> rv = device_create_file(intf->si_dev, &intf->maintenance_mode_devattr);
> if (rv) {
> + device_remove_file(intf->si_dev, &intf->nr_msgs_devattr);
> device_remove_file(intf->si_dev, &intf->nr_users_devattr);
> goto out_err_bmc_reg;
> }
> --
> 2.43.0
>
prev parent reply other threads:[~2026-08-03 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 1:55 [PATCH v1] ipmi: Remove all sysfs files on registration failure Yuho Choi
2026-08-03 15:20 ` Corey Minyard [this message]
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=anCx1qbu3miWg2lI@mail.minyard.net \
--to=corey@minyard.net \
--cc=dbgh9129@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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