mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	mm-commits@vger.kernel.org
Subject: [GIT PULL] hotfixes for 7.1-rc7
Date: Mon, 1 Jun 2026 21:05:27 -0700	[thread overview]
Message-ID: <20260601210527.ad1549849df4d9d58b12cffe@linux-foundation.org> (raw)


Linus, please merge this batch of hotfixes, thanks.

The following changes since commit d60ec36cab338dfe2ae40d73e9c8d6c4af70d2b8:

  Merge tag 'mm-hotfixes-stable-2026-05-25-16-22' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2026-05-26 08:23:19 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2026-06-01-20-58

for you to fetch changes up to 9d7bea186ba5a002456471edf36cc9b69f809397:

  userfaultfd: remove redundant check in vm_uffd_ops() (2026-05-31 21:50:26 -0700)

----------------------------------------------------------------
13 hotfixes.  All are for MM.  10 are cc:stable and the remaining 3
address post-7.1 issues or aren't considered suitable for backporting.

There's a 3 patch series "userfaultfd: verify VMA state across UFFDIO_COPY
retry" from Mike Rapoport which fixes a few uffd things.  The rest are
singletons - please see the individual changelogs for details.

----------------------------------------------------------------
David Carlier (1):
      mm/hugetlb: restore reservation on error in hugetlb folio copy paths

Lorenzo Stoakes (1):
      mm/hugetlb: avoid false positive lockdep assertion

Mike Rapoport (Microsoft) (3):
      userfaultfd: verify VMA state across UFFDIO_COPY retry
      userfaultfd: refuse to __mfill_atomic_pte() for unsupported VMAs
      userfaultfd: remove redundant check in vm_uffd_ops()

Muchun Song (3):
      mm/cma_debug: fix invalid accesses for inactive CMA areas
      mm/cma: fix reserved page leak on activation failure
      mm/hugetlb_vmemmap: fix incorrect vmemmap restore in rollback

SeongJae Park (1):
      mm/damon/ops-common: call folio_test_lru() after folio_get()

Shakeel Butt (1):
      memcg: use round-robin victim selection in refill_stock

Wupeng Ma (1):
      mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison

Yin Tirui (2):
      mm/huge_memory: update file PUD counter before folio_put()
      mm/huge_memory: update file PMD counter before folio_put()

 include/linux/hugetlb.h |  8 -----
 include/linux/mm.h      |  8 -----
 mm/cma.c                |  7 ++--
 mm/cma_debug.c          |  3 +-
 mm/damon/ops-common.c   |  4 +--
 mm/huge_memory.c        |  4 ++-
 mm/hugetlb.c            | 69 +++++++++++++++++++++----------------
 mm/hugetlb_vmemmap.c    | 36 +++++++++----------
 mm/memcontrol.c         |  5 ++-
 mm/memory-failure.c     | 19 +++++-----
 mm/userfaultfd.c        | 92 ++++++++++++++++++++++++++++++++++++++++++-------
 11 files changed, 162 insertions(+), 93 deletions(-)


             reply	other threads:[~2026-06-02  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  4:05 Andrew Morton [this message]
2026-06-02 18:09 ` pr-tracker-bot

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=20260601210527.ad1549849df4d9d58b12cffe@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=torvalds@linuxfoundation.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®