From: Corey Minyard <corey@minyard.net>
To: Breno Leitao <leitao@debian.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
kernel-team@meta.com
Subject: Re: [PATCH 2/2] ipmi: Consolidate the run to completion checking for xmit msgs lock
Date: Tue, 27 Jan 2026 08:46:06 -0600 [thread overview]
Message-ID: <aXjPrnG7ErymtHBx@mail.minyard.net> (raw)
In-Reply-To: <aXjOT9e11GSrMHiy@gmail.com>
On Tue, Jan 27, 2026 at 06:41:48AM -0800, Breno Leitao wrote:
> On Tue, Jan 27, 2026 at 07:54:40AM -0600, Corey Minyard wrote:
> > It made things hard to read, move the check to a function.
> >
> > Signed-off-by: Corey Minyard <corey@minyard.net>
> > ---
> > drivers/char/ipmi/ipmi_msghandler.c | 40 ++++++++++++++++-------------
> > 1 file changed, 22 insertions(+), 18 deletions(-)
> >
> > diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c
> > index a590a67294e2..030828cdb778 100644
> > --- a/drivers/char/ipmi/ipmi_msghandler.c
> > +++ b/drivers/char/ipmi/ipmi_msghandler.c
> > @@ -602,6 +602,20 @@ static int __ipmi_bmc_register(struct ipmi_smi *intf,
> > static int __scan_channels(struct ipmi_smi *intf,
> > struct ipmi_device_id *id, bool rescan);
> >
> > +static void ipmi_lock_xmit_msgs(struct ipmi_smi *intf, int run_to_completion,
> > + unsigned long *flags)
> > +{
> > + if (!run_to_completion)
> > + spin_lock_irqsave(&intf->xmit_msgs_lock, *flags);
> > +}
>
> I usually see the opposite construction in most cases. Something like:
>
> static void ipmi_lock_xmit_msgs(struct ipmi_smi *intf, int run_to_completion,
> unsigned long *flags)
> {
> if (run_to_completion)
> return;
>
> spin_lock_irqsave(&intf->xmit_msgs_lock, *flags);
> }
Yes, that's better, I've changed it.
>
> Thanks for doing this, this looks way better!
No problem. It was more for my own benefit :-).
-corey
> --breno
next prev parent reply other threads:[~2026-01-27 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 9:57 [PATCH] ipmi: fix NULL pointer on smi_work Breno Leitao
2026-01-27 9:57 ` [PATCH] ipmi: Fix use-after-free and list corruption on sender error Breno Leitao
2026-01-27 13:22 ` Corey Minyard
2026-01-27 13:54 ` Corey Minyard
2026-01-27 13:54 ` [PATCH 1/2] ipmi: Fix use-after-free and list corruption on sender error Corey Minyard
2026-01-27 14:40 ` Breno Leitao
2026-01-27 14:46 ` Corey Minyard
2026-01-27 13:54 ` [PATCH 2/2] ipmi: Consolidate the run to completion checking for xmit msgs lock Corey Minyard
2026-01-27 14:41 ` Breno Leitao
2026-01-27 14:46 ` Corey Minyard [this message]
2026-01-27 14:53 ` Breno Leitao
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=aXjPrnG7ErymtHBx@mail.minyard.net \
--to=corey@minyard.net \
--cc=justinstitt@google.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--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