public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <corey@minyard.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	openipmi-developer@lists.sourceforge.net,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Igor Raits <igor@gooddata.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Matt Johnston <matt@codeconstruct.com.au>,
	Breno Leitao <leitao@debian.org>
Subject: [GIT PULL] IPMI bug fixes for 7.0
Date: Thu, 26 Feb 2026 12:48:12 -0600	[thread overview]
Message-ID: <aaCVbFXCsGMJmaeq@mail.minyard.net> (raw)

The following changes since commit b71e635feefc852405b14620a7fc58c4c80c0f73:

  Merge tag 'cgroup-for-6.19-rc5-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup (2026-01-12 09:56:17 -1000)

are available in the Git repository at:

  https://github.com/cminyard/linux-ipmi.git tags/for-linus-7.0-1

for you to fetch changes up to cae66f1a1dcd23e17da5a015ef9d731129f9d2dd:

  ipmi:si: Fix check for a misbehaving BMC (2026-02-23 09:00:48 -0600)

----------------------------------------------------------------
Bug fixes for the IPMI driver

I apologise for this being late, I wanted to leave it in the next tree
for a while, and the work I did came in late, but I really don't want to
ship 7.0 with these issues.   It's been in the next tree since Feb 13,
and I had to rebase on Feb 23 to add a missed review and to fold in a
fix that didn't make sense by itself.

This mostly revolves around getting the driver to behave when the IPMI
device misbehaves.  Past attempts have not worked very well because I
didn't have hardware I couldmake do this, and AI was fairly useless for
help on this.

So I modified qemu and my test suite so I could reproduce a misbehaving
IPMI device, and with that I was able to fix the issues.

----------------------------------------------------------------
Corey Minyard (8):
      ipmi: Fix use-after-free and list corruption on sender error
      ipmi: Consolidate the run to completion checking for xmit msgs lock
      ipmi:ls2k: Make ipmi_ls2k_platform_driver static
      ipmi:si: Handle waiting messages when BMC failure detected
      ipmi:si: Use a long timeout when the BMC is misbehaving
      ipmi:si: Don't block module unload if the BMC is messed up
      ipmi:msghandler: Handle error returns from the SMI sender
      ipmi:si: Fix check for a misbehaving BMC

Matt Johnston (1):
      ipmi: ipmb: initialise event handler read bytes

 drivers/char/ipmi/ipmi_ipmb.c       |   5 ++
 drivers/char/ipmi/ipmi_msghandler.c | 141 ++++++++++++++++++++++++------------
 drivers/char/ipmi/ipmi_si_intf.c    |  37 ++++++----
 drivers/char/ipmi/ipmi_si_ls2k.c    |   2 +-
 4 files changed, 125 insertions(+), 60 deletions(-)

             reply	other threads:[~2026-02-26 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 18:48 Corey Minyard [this message]
2026-02-27  1:57 ` [GIT PULL] IPMI bug fixes for 7.0 pr-tracker-bot

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=aaCVbFXCsGMJmaeq@mail.minyard.net \
    --to=corey@minyard.net \
    --cc=igor@gooddata.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matt@codeconstruct.com.au \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=rafael@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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