linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, x86@kernel.org,
	David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Christoph Hellwig <hch@lst.de>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andy Lutomirski <luto@kernel.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Fei Li <fei1.li@intel.com>, Nathan Chancellor <nathan@kernel.org>
Subject: [PATCH v2 0/3] x86/mm/pat: fix VM_PAT handling in COW mappings
Date: Wed,  3 Apr 2024 23:21:28 +0200	[thread overview]
Message-ID: <20240403212131.929421-1-david@redhat.com> (raw)

Rebased on latest mm-unstable. As we have a conflict now with a cleanup
from Chrostoph, temporarily revert that one, so we can apply the fix,
and reapply the adjusted cleanup on top. I squashed the fixups
sitting in Andrew's tree for that patch.

The fix should likely go in first via the hotfix route, that's why I'm
moving it to the front.

Tested with my reproducer.

v1 -> v2:
 * Rebased to latest mm-unstable
 * "x86/mm/pat: fix VM_PAT handling in COW mappings"
  -> Fix function parameter indentation
  -> Add Ingos Ack

Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Fei Li <fei1.li@intel.com>
Cc: Nathan Chancellor <nathan@kernel.org>

Christoph Hellwig (1):
  mm: move follow_phys to arch/x86/mm/pat/memtype.c

David Hildenbrand (2):
  [mm-unstable] Revert "mm: move follow_phys to
    arch/x86/mm/pat/memtype.c"
  x86/mm/pat: fix VM_PAT handling in COW mappings

 arch/x86/mm/pat/memtype.c | 56 +++++++++++++++++++++++++++++----------
 1 file changed, 42 insertions(+), 14 deletions(-)

-- 
2.44.0



             reply	other threads:[~2024-04-03 21:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 21:21 David Hildenbrand [this message]
2024-04-03 21:21 ` [PATCH v2 1/3] [mm-unstable] Revert "mm: move follow_phys to arch/x86/mm/pat/memtype.c" David Hildenbrand
2024-04-03 21:21 ` [PATCH v2 2/3] x86/mm/pat: fix VM_PAT handling in COW mappings David Hildenbrand
2024-04-03 22:12   ` Andrew Morton
2024-04-04 19:20     ` David Hildenbrand
2024-04-04 20:01       ` Andrew Morton
2024-04-07  2:08   ` mawupeng
2024-04-03 21:21 ` [PATCH v2 3/3] mm: move follow_phys to arch/x86/mm/pat/memtype.c David Hildenbrand
2024-04-03 22:09 ` [PATCH v2 0/3] x86/mm/pat: fix VM_PAT handling in COW mappings Andrew Morton
2024-04-05  7:00   ` Christoph Hellwig

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=20240403212131.929421-1-david@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=fei1.li@intel.com \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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