From: Sasha Levin <sashal@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: stable@vger.kernel.org
Subject: Re: v6.5 backport request: 6d2779ecaeb56f92 ("locking/atomic: scripts: fix fallback ifdeffery")
Date: Tue, 3 Oct 2023 12:37:45 -0400 [thread overview]
Message-ID: <ZRxDWQop/3kdbObN@sashalap> (raw)
In-Reply-To: <ZRw-0snchQiF5shv@FVFF77S0Q05N>
On Tue, Oct 03, 2023 at 05:18:26PM +0100, Mark Rutland wrote:
>Hi,
>
>Could we please backport commit:
>
> 6d2779ecaeb56f92d7105c56772346c71c88c278
> ("locking/atomic: scripts: fix fallback ifdeffery")
>
>... to the 6.5.y stable tree?
>
>I forgot to Cc stable when I submitted the original patch, and had (mistakenly)
>assumed that the Fixes tag was sufficient.
>
>The patch fixes a dentry cache corruption issue observed on arm64 and which is
>in theory possible on other architectures. I've recevied an off-list report
>from someone who's hit the issue on the v6.5.y tree specifically.
Already done, it came in via AUTOSEL.
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-10-03 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 16:18 v6.5 backport request: 6d2779ecaeb56f92 ("locking/atomic: scripts: fix fallback ifdeffery") Mark Rutland
2023-10-03 16:37 ` Sasha Levin [this message]
2023-10-04 9:14 ` Mark Rutland
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=ZRxDWQop/3kdbObN@sashalap \
--to=sashal@kernel.org \
--cc=mark.rutland@arm.com \
--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