From: Corey Minyard <minyard@acm.org>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Chengfeng Ye <dg573847474@gmail.com>
Subject: Re: [PATCH] ipmi: fix potential deadlock on &kcs_bmc->lock
Date: Wed, 28 Jun 2023 06:47:29 -0500 [thread overview]
Message-ID: <ZJwd0UDKYcK9AvSf@mail.minyard.net> (raw)
In-Reply-To: <20230627152449.36093-1-dg573847474@gmail.com>
Indeed, this looks like an issue.
Andrew, any opinions on this? The attached patch will work, the other
option would be to disable interrupts when calling
kcs_bmc_handle_event() in the timer handler. But then you have to worry
about RT.
-corey
On Tue, Jun 27, 2023 at 03:24:49PM +0000, Chengfeng Ye wrote:
> As kcs_bmc_handle_event() is executed inside both a timer and a hardirq,
> it should disable irq before lock acquisition otherwise deadlock could
> happen if the timmer is preemtped by the irq.
>
> Possible deadlock scenario:
> aspeed_kcs_check_obe() (timer)
> -> kcs_bmc_handle_event()
> -> spin_lock(&kcs_bmc->lock)
> <irq interruption>
> -> aspeed_kcs_irq()
> -> kcs_bmc_handle_event()
> -> spin_lock(&kcs_bmc->lock) (deadlock here)
>
> This flaw was found using an experimental static analysis tool we are
> developing for irq-related deadlock.
>
> The tentative patch fix the potential deadlock by spin_lock_irqsave()
>
> Signed-off-by: Chengfeng Ye <dg573847474@gmail.com>
> ---
> drivers/char/ipmi/kcs_bmc.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/char/ipmi/kcs_bmc.c b/drivers/char/ipmi/kcs_bmc.c
> index 03d02a848f3a..8b1161d5194a 100644
> --- a/drivers/char/ipmi/kcs_bmc.c
> +++ b/drivers/char/ipmi/kcs_bmc.c
> @@ -56,12 +56,13 @@ irqreturn_t kcs_bmc_handle_event(struct kcs_bmc_device *kcs_bmc)
> {
> struct kcs_bmc_client *client;
> irqreturn_t rc = IRQ_NONE;
> + unsigned long flags;
>
> - spin_lock(&kcs_bmc->lock);
> + spin_lock_irqsave(&kcs_bmc->lock, flags);
> client = kcs_bmc->client;
> if (client)
> rc = client->ops->event(client);
> - spin_unlock(&kcs_bmc->lock);
> + spin_unlock_irqrestore(&kcs_bmc->lock, flags);
>
> return rc;
> }
> --
> 2.17.1
>
next prev parent reply other threads:[~2023-06-28 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 15:24 [PATCH] ipmi: fix potential deadlock on &kcs_bmc->lock Chengfeng Ye
2023-06-28 11:47 ` Corey Minyard [this message]
2023-06-30 1:01 ` Andrew Jeffery
2023-07-04 14:27 ` Corey Minyard
2023-07-04 16:25 ` Chengfeng Ye
2023-07-05 12:00 ` Andrew Jeffery
2023-07-19 18:37 ` Chengfeng Ye
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=ZJwd0UDKYcK9AvSf@mail.minyard.net \
--to=minyard@acm.org \
--cc=andrew@aj.id.au \
--cc=dg573847474@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