Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Kiryl Shutsemau <kas@kernel.org>,
	Vernon Yang <vernon2gm@gmail.com>,
	rick.p.edgecombe@intel.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,
	tj@kernel.org, rppt@kernel.org, yu-cheng.yu@intel.com,
	orsonpeters@gmail.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 10:21:30 -0700	[thread overview]
Message-ID: <20260903102130.b5cda1b08f3efd4ab66226e9@linux-foundation.org> (raw)
In-Reply-To: <314f11c1-ce5e-4b36-b296-0ab742550851@intel.com>

On Thu, 3 Sep 2026 07:18:54 -0700 Dave Hansen <dave.hansen@intel.com> wrote:

> On 9/3/26 04:54, Kiryl Shutsemau wrote:
> >> Closes: https://lore.kernel.org/r/CAJxLxMUGu1-L+O_nAONOwOXnS=cNbNApCWqdthRjd76LThtSPg@mail.gmail.com/
> >> Fixes: bb3aadf7d446 ("x86/mm: Start actually marking _PAGE_SAVED_DIRTY")
> > Hm. I don't understand why would this commit explicitly exclude
> > _PAGE_DIRTY from the mask:
> > 
> > -       val &= _HPAGE_CHG_MASK;
> > +       val &= (_HPAGE_CHG_MASK & ~_PAGE_DIRTY);
> > 
> > Rick, could you comment? It doesn't look like a typo.
> 
> My guess is that it's some remnant from an earlier version of the patch.
> The asymmetry with pte_modify() vs. pmd_modify() just can't be explained
> any other way. It _might_ have been some attempt to say, "Hey
> _PAGE_DIRTY is now a part of the pgprot_t since it's part of the
> 'permissions' of a shadow stack PTE" that got abandoned.
> 
> But I don't see anything wrong with the fix at all.
> 
> It does give me pause that this has been losing user data for so long,
> but it must just be a weird combination of features that few folks use
> together (huge pages + MADV_FREE).
> 

And with heavy reclaim pressure.


  reply	other threads:[~2026-09-03 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03  3:16 [PATCH] x86/mm: Fix pmd_modify() dropping the dirty bit 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
2026-09-03 11:54 ` Kiryl Shutsemau
2026-09-03 14:18   ` Dave Hansen
2026-09-03 17:21     ` Andrew Morton [this message]
2026-09-03 17:58     ` Edgecombe, Rick P
2026-09-03 18:01       ` Dave Hansen
2026-09-03 18:33         ` Edgecombe, Rick P

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=20260903102130.b5cda1b08f3efd4ab66226e9@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andrew+kernel@donnellan.id.au \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --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