From: Dave Hansen <dave.hansen@intel.com>
To: Orson Peters <orsonpeters@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Vernon Yang <vernon2gm@gmail.com>,
tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, david@kernel.org, hpa@zytor.com,
rmclure@linux.ibm.com, andrew+kernel@donnellan.id.au,
pasha.tatashin@soleen.com, kas@kernel.org, tj@kernel.org,
rppt@kernel.org, rick.p.edgecombe@intel.com,
yu-cheng.yu@intel.com, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-mm@kvack.org,
Vernon Yang <yanglincheng@kylinos.cn>,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/mm: Fix pmd_modify() dropping the dirty bit
Date: Thu, 3 Sep 2026 08:40:10 -0700 [thread overview]
Message-ID: <8e68ef0b-d88d-4b44-9740-717463550465@intel.com> (raw)
In-Reply-To: <CAJxLxMXN+y03VPWyiLcT5-eLVGE8iojDm4+GYd5fdJ4ZtQ45UQ@mail.gmail.com>
On 9/3/26 00:34, Orson Peters wrote:
> Considering that the impact is so severe if the bug does occur (silent
> memory corruption), will there be backports of this patch? If I'm not
> mistaken the offending line that introduced the bug was first released
> in version 6.6.
Hi Orson,
It's tagged for stable@ so it should hit the stable trees at some point
and make it into the 6.6 series.
next prev parent reply other threads:[~2026-09-03 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 3:16 Vernon Yang
2026-09-03 4:10 ` Andrew Morton
2026-09-03 5:24 ` Vernon Yang
2026-09-03 7:34 ` Orson Peters
2026-09-03 15:40 ` Dave Hansen [this message]
2026-09-03 11:54 ` Kiryl Shutsemau
2026-09-03 14:18 ` Dave Hansen
2026-09-03 17:21 ` Andrew Morton
2026-09-03 17:58 ` Edgecombe, Rick P
2026-09-03 18:01 ` Dave Hansen
2026-09-03 18:33 ` Edgecombe, Rick P
2026-09-03 19:25 ` [tip: x86/urgent] x86/mm: Fix userspace data loss with MADV_FREE and THP tip-bot2 for Vernon Yang
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=8e68ef0b-d88d-4b44-9740-717463550465@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew+kernel@donnellan.id.au \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=orsonpeters@gmail.com \
--cc=pasha.tatashin@soleen.com \
--cc=rick.p.edgecombe@intel.com \
--cc=rmclure@linux.ibm.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=tj@kernel.org \
--cc=vernon2gm@gmail.com \
--cc=x86@kernel.org \
--cc=yanglincheng@kylinos.cn \
--cc=yu-cheng.yu@intel.com \
/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
all inboxes | Powered by JetHome®