From: Greg KH <gregkh@linuxfoundation.org>
To: Armin Wolf <W_Armin@gmx.de>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: Patch "platform/x86: xiaomi-wmi: Fix race condition when reporting key events" has been added to the 6.6-stable tree
Date: Wed, 12 Jun 2024 14:40:40 +0200 [thread overview]
Message-ID: <2024061223-deceiver-other-dc06@gregkh> (raw)
In-Reply-To: <d691d3c3-1cb7-44c1-85f0-ecc3c74e966f@gmx.de>
On Mon, May 27, 2024 at 12:59:49AM +0200, Armin Wolf wrote:
> Am 26.05.24 um 21:43 schrieb Sasha Levin:
>
> > This is a note to let you know that I've just added the patch titled
> >
> > platform/x86: xiaomi-wmi: Fix race condition when reporting key events
> >
> > to the 6.6-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > platform-x86-xiaomi-wmi-fix-race-condition-when-repo.patch
> > and it can be found in the queue-6.6 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> Hi,
>
> the underlying race condition can only be triggered since
> commit e2ffcda16290 ("ACPI: OSL: Allow Notify () handlers to run on all CPUs"), which
> afaik was introduced with kernel 6.8.
>
> Because of this, i do not think that we have to backport this commit to kernels before 6.8.
Thanks for looking into this and letting us know!
greg k-h
prev parent reply other threads:[~2024-06-12 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240526194314.3503546-1-sashal@kernel.org>
2024-05-26 22:59 ` Patch "platform/x86: xiaomi-wmi: Fix race condition when reporting key events" has been added to the 6.6-stable tree Armin Wolf
2024-06-12 12:40 ` Greg KH [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=2024061223-deceiver-other-dc06@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=stable-commits@vger.kernel.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