From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Corey Minyard <minyard@acm.org>
Cc: stable@vger.kernel.org,
"Janne Huttunen (Nokia)" <janne.huttunen@nokia.com>
Subject: Re: Request for backport 4.19 for the IPMI driver
Date: Wed, 21 Jun 2023 20:39:16 +0200 [thread overview]
Message-ID: <2023062157-relic-rogue-65a2@gregkh> (raw)
In-Reply-To: <ZJGWHhJJeuiP1H18@mail.minyard.net>
On Tue, Jun 20, 2023 at 07:05:50AM -0500, Corey Minyard wrote:
> Please backport the following changes to the 4.18 stable kernel:
>
> e1891cffd4c4 "ipmi: Make the smi watcher be disabled immediately when not needed"
> 383035211c79 "ipmi: move message error checking to avoid deadlock"
>
> e1891cffd4c4 doesn't apply completely cleanly because of other changes,
> but you just need to leave in the free_user_work() function and delete
> the other function in the conflict. I can also supply a patch if
> necessary.
>
> Change
>
> b4a34aa6d "ipmi: Fix how the lower layers are told to watch for messages"
>
> was backported to fullfill a dependency for another backport, but there
> was another change:
>
> e1891cffd4c4 "ipmi: Make the smi watcher be disabled immediately when not needed"
>
> That is needed to avoid calling a lower layer function with
> xmit_msgs_lock held. In addition to that, you will also need:
>
> 383035211c79 "ipmi: move message error checking to avoid deadlock"
>
> to fix a bug in that change.
>
> e1891cffd4c4 came in 5.1 and 383035211c79 came in 5.4 (and I believe was
> backported) so everything should be good for 5.4 and later. b4a34aa6d
> was not backported to 4.14, so it is also ok. So 4.19 is the only
> kernel that needs the change.
>
> Thanks to Janne Huttunen for quick work on this.
Thanks for this, both now queued up.
greg k-h
prev parent reply other threads:[~2023-06-21 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 12:05 Request for backport 4.19 for the IPMI driver Corey Minyard
2023-06-21 18:39 ` Greg Kroah-Hartman [this message]
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=2023062157-relic-rogue-65a2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=janne.huttunen@nokia.com \
--cc=minyard@acm.org \
--cc=stable@vger.kernel.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