mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Liam R. Howlett" <liam@infradead.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>, Jann Horn <jannh@google.com>,
	Pedro Falcato <pfalcato@suse.de>,
	Oscar Salvador <osalvador@suse.de>,
	Miaohe Lin <linmiaohe@huawei.com>,
	Naoya Horiguchi <nao.horiguchi@gmail.com>,
	Adam Litke <agl@us.ibm.com>, Mel Gorman <mel@csn.ul.ie>,
	Rik van Riel <riel@surriel.com>, Peter Xu <peterx@redhat.com>,
	"Kiryl Shutsemau (Meta)" <kas@kernel.org>,
	"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
	Josef Bacik <josef@toxicpanda.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Chris Mason <mason@kernel.org>
Subject: Re: [PATCH 00/10] mm: various (urgent?) fixes
Date: Fri, 16 Oct 2026 15:15:44 +0800	[thread overview]
Message-ID: <A061083A-3A02-4ADB-9CFB-7CF6C731A872@linux.dev> (raw)
In-Reply-To: <20261015-urgent_fixes-v1-0-42796911043b@kernel.org>



> On Oct 16, 2026, at 00:07, David Hildenbrand (Arm) <david@kernel.org> wrote:
> 
> Hi,
> 
> here are various MM fixes. The majority was reported by Josef at
> Anthrophic, the remainder was found while reviewing/overhauling them.
> 
> Two issues/fixes reported are not included, as we are discussing
> (better) alternatives on the list already.
> 
> I left most of the original commit messages as schloppy as they are: I
> don't particularly care as long as the code is in good shape and as long as
> they are not actively wrong. But I (and Mike) could not be stopped from
> overhauling at least some of them.
> 
> While I don't think there is anything too critical in here, I think this
> is a good opportunity to see how fast we can get pre-screened/pre-reviewed
> fixes upstream that might be security-related.
> 
> The majority are hugetlb + uffd issues, that are not actually that
> relevant for most installations. But all things that should just get
> fixed. Some uffd fixes need proper follow ups to fix some more of the
> root causes of leftover UFFD PTE bits (or proof that there are none
> remaining).
> 
> I ran some MM selftests and nothing popped up.
> 
> So let's try to get these upstream in a timely fashion.
> 
> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
> ---
> David Hildenbrand (Arm) (4):
>      mm/hugetlb: fix use-after-free in hugetlb_mfill_atomic_pte()
>      mm/hugetlb: tolerate uffd bits set without uffd for PROT_NONE PTEs
>      mm/hugetlb: tolerate UFFD_WP markers outside uffd-wp VMAs
>      mm/mremap: fix calling fixup_hugetlb_reservations() on the wrong VMA
> 
> Josef Bacik (6):
>      mm/vma: don't leak the commit charge on mmap failure
>      mm/hugetlb: fix use-after-free of a new anon folio
>      mm/hugetlb: unmap the page where the other VMA maps it
>      mm/hugetlb: don't clear the resv_map of a VMA whose lock is held
>      mm/hugetlb: fix endless write fault on a leftover uffd bit
>      mm/hugetlb: don't leave a uffd-wp marker when zapping an RWP entry

HugeTLB is really nasty, while no new features are landing, we have a steady
stream of bug fixes coming in.

Thanks,
Muchun

> 
> mm/hugetlb.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++--------------
> mm/mremap.c  |  2 +-
> mm/vma.c     | 11 ++++++----
> 3 files changed, 62 insertions(+), 21 deletions(-)
> 
> ---
> 
> base-commit: 0fcb05b72344f40806cbe810de8872f1698bf053
> 
> change-id: 20261015-urgent_fixes-7112629346eb
> 
> --
> 
> Cheers,
> 
> David
> 


  parent reply	other threads:[~2026-10-16  7:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 16:07 David Hildenbrand (Arm)
2026-10-15 16:07 ` [PATCH 01/10] mm/vma: don't leak the commit charge on mmap failure David Hildenbrand (Arm)
2026-10-15 17:54   ` Pedro Falcato
2026-10-15 18:53     ` David Hildenbrand (Arm)
2026-10-16  8:34   ` Jose A. Perez de Azpillaga
2026-10-15 16:07 ` [PATCH 02/10] mm/hugetlb: fix use-after-free of a new anon folio David Hildenbrand (Arm)
2026-10-16  7:16   ` Muchun Song
2026-10-15 16:07 ` [PATCH 03/10] mm/hugetlb: fix use-after-free in hugetlb_mfill_atomic_pte() David Hildenbrand (Arm)
2026-10-16  7:18   ` Muchun Song
2026-10-15 16:07 ` [PATCH 04/10] mm/hugetlb: unmap the page where the other VMA maps it David Hildenbrand (Arm)
2026-10-16  9:49   ` Muchun Song
2026-10-15 16:07 ` [PATCH 05/10] mm/hugetlb: don't clear the resv_map of a VMA whose lock is held David Hildenbrand (Arm)
2026-10-16  9:52   ` Muchun Song
2026-10-15 16:07 ` [PATCH 06/10] mm/hugetlb: fix endless write fault on a leftover uffd bit David Hildenbrand (Arm)
2026-10-15 20:10   ` Lorenzo Stoakes (ARM)
2026-10-15 16:07 ` [PATCH 07/10] mm/hugetlb: tolerate uffd bits set without uffd for PROT_NONE PTEs David Hildenbrand (Arm)
2026-10-15 20:13   ` Lorenzo Stoakes (ARM)
2026-10-15 16:07 ` [PATCH 08/10] mm/hugetlb: tolerate UFFD_WP markers outside uffd-wp VMAs David Hildenbrand (Arm)
2026-10-15 19:47   ` Lorenzo Stoakes (ARM)
2026-10-15 16:07 ` [PATCH 09/10] mm/hugetlb: don't leave a uffd-wp marker when zapping an RWP entry David Hildenbrand (Arm)
2026-10-15 19:45   ` Lorenzo Stoakes (ARM)
2026-10-15 16:07 ` [PATCH 10/10] mm/mremap: fix calling fixup_hugetlb_reservations() on the wrong VMA David Hildenbrand (Arm)
2026-10-16  9:53   ` Muchun Song
2026-10-16  7:15 ` Muchun Song [this message]
2026-10-16  7:40   ` [PATCH 00/10] mm: various (urgent?) fixes David Hildenbrand (Arm)

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=A061083A-3A02-4ADB-9CFB-7CF6C731A872@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=agl@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=jannh@google.com \
    --cc=josef@toxicpanda.com \
    --cc=kas@kernel.org \
    --cc=liam@infradead.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mason@kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=nao.horiguchi@gmail.com \
    --cc=osalvador@suse.de \
    --cc=peterx@redhat.com \
    --cc=pfalcato@suse.de \
    --cc=riel@surriel.com \
    --cc=rppt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@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

all inboxes | Powered by JetHome®