From: Corey Minyard <corey@minyard.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Greg Thelen <gthelen@google.com>
Subject: Re: [PATCH] ipmi: Fix handling of messages with provided receive message pointer
Date: Tue, 7 Oct 2025 06:45:55 -0500 [thread overview]
Message-ID: <aOT9c1ULJolUHPSA@mail.minyard.net> (raw)
In-Reply-To: <20251006201857.3433837-1-linux@roeck-us.net>
On Mon, Oct 06, 2025 at 01:18:57PM -0700, Guenter Roeck wrote:
> Prior to commit b52da4054ee0 ("ipmi: Rework user message limit handling"),
> i_ipmi_request() used to increase the user reference counter if the receive
> message is provided by the caller of IPMI API functions. This is no longer
> the case. However, ipmi_free_recv_msg() is still called and decreases the
> reference counter. This results in the reference counter reaching zero,
> the user data pointer is released, and all kinds of interesting crashes are
> seen.
>
> Fix the problem by increasing user reference counter if the receive message
> has been provided by the caller.
Yes, the only interface that uses this that would matter is the watchdog
timer, which my tests don't currently cover. I guess I need to add some
tests.
Sorry, and thanks for the fix. It's queued for next release.
-corey
>
> Fixes: b52da4054ee0 ("ipmi: Rework user message limit handling")
> Reported-by: Eric Dumazet <edumazet@google.com>
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: Greg Thelen <gthelen@google.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/char/ipmi/ipmi_msghandler.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c
> index a0b67a35a5f0..3700ab4eba3e 100644
> --- a/drivers/char/ipmi/ipmi_msghandler.c
> +++ b/drivers/char/ipmi/ipmi_msghandler.c
> @@ -2301,8 +2301,11 @@ static int i_ipmi_request(struct ipmi_user *user,
> if (supplied_recv) {
> recv_msg = supplied_recv;
> recv_msg->user = user;
> - if (user)
> + if (user) {
> atomic_inc(&user->nr_msgs);
> + /* The put happens when the message is freed. */
> + kref_get(&user->refcount);
> + }
> } else {
> recv_msg = ipmi_alloc_recv_msg(user);
> if (IS_ERR(recv_msg))
> --
> 2.45.2
>
next prev parent reply other threads:[~2025-10-07 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 20:18 Guenter Roeck
2025-10-07 11:45 ` Corey Minyard [this message]
2025-10-07 11:46 ` Corey Minyard
2025-10-07 13:50 ` Guenter Roeck
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=aOT9c1ULJolUHPSA@mail.minyard.net \
--to=corey@minyard.net \
--cc=edumazet@google.com \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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
all inboxes | Powered by JetHome®