public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	openipmi-developer@lists.sourceforge.net
Subject: [GIT PULL] IPMI bug fixes for 5.17 (second set)
Date: Wed, 4 May 2022 06:50:47 -0500	[thread overview]
Message-ID: <20220504115047.GC3767252@minyard.net> (raw)

The following changes since commit ae085d7f9365de7da27ab5c0d16b12d51ea7fca9:

  mm: kfence: fix missing objcg housekeeping for SLAB (2022-03-27 18:47:00 -0700)

are available in the Git repository at:

  https://github.com/cminyard/linux-ipmi.git tags/for-linus-5.17-2

for you to fetch changes up to 9cc3aac42566a0021e0ab7c4e9b31667ad75b1e3:

  ipmi:ipmi_ipmb: Fix null-ptr-deref in ipmi_unregister_smi() (2022-04-29 10:06:52 -0500)

----------------------------------------------------------------
Fix some issues that were reported

This has been in for-next for a bit (longer than the times would
indicate, I had to rebase to add some text to the headers) and these are
fixes that need to go in.

----------------------------------------------------------------
Corey Minyard (2):
      ipmi: When handling send message responses, don't process the message
      ipmi:ipmi_ipmb: Fix null-ptr-deref in ipmi_unregister_smi()

 drivers/char/ipmi/ipmi_msghandler.c | 7 ++++++-
 drivers/char/ipmi/ipmi_si_intf.c    | 5 +----
 2 files changed, 7 insertions(+), 5 deletions(-)

             reply	other threads:[~2022-05-04 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 11:50 Corey Minyard [this message]
2022-05-04 18:24 ` [GIT PULL] IPMI bug fixes for 5.17 (second set) 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=20220504115047.GC3767252@minyard.net \
    --to=minyard@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --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