mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Corey Minyard" <minyard@acm.org>
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, 05 Jul 2023 21:30:38 +0930	[thread overview]
Message-ID: <34c75a2f-2daa-49be-bdca-a3fff5ed5a4a@app.fastmail.com> (raw)
In-Reply-To: <ZKQsY3DXXDbxy0om@mail.minyard.net>



On Tue, 4 Jul 2023, at 23:57, Corey Minyard wrote:
> On Fri, Jun 30, 2023 at 10:31:02AM +0930, Andrew Jeffery wrote:
>> Hi Corey, Chengfeng,
>> 
>> On Wed, 28 Jun 2023, at 21:17, Corey Minyard wrote:
>> > 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.
>> 
>> Right, I think we'd do best to not over-complicate things.
>> spin_lock_irq{save,restore}() are the intuitive choice to me.
>> 
>> I'll follow up with R-b/T-b tags once I've booted the patch
>> and done some testing.
>
> Thanks.  This is in my for-next tree, I'd like to get this in the merge
> window, which I believe ends this Sunday.
>

I've successfully booted an IBM Rainier machine with this patch 
applied. Rainier is a Power10-based platform managed by an AST2600 BMC. 
The boot process makes heavy use of one of the KCS devices as part of 
an MCTP transport binding implementation between the BMC and host 
firmware.

Reviewed-by: Andrew Jeffery <andrew@aj.id.au>
Tested-by: Andrew Jeffery <andrew@aj.id.au>

Thanks,

Andrew

  parent reply	other threads:[~2023-07-05 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 15:24 Chengfeng Ye
2023-06-28 11:47 ` Corey Minyard
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 [this message]
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=34c75a2f-2daa-49be-bdca-a3fff5ed5a4a@app.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=dg573847474@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.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

all inboxes | Powered by JetHome®