linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] hotfixes for 6.17-rc2
Date: Tue, 12 Aug 2025 20:52:56 -0700	[thread overview]
Message-ID: <20250812205256.7782e2e483a8b12774e65dcd@linux-foundation.org> (raw)


Linus, please pull this batch of hotfixes, thanks.


The following changes since commit 6bcdbd62bd56e6d7383f9e06d9d148935b3c9b73:

  Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rmk/linux (2025-08-05 16:55:03 +0300)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2025-08-12-20-50

for you to fetch changes up to c0e1b774f68bdbea1618e356e30672c7f1e32509:

  proc: proc_maps_open allow proc_mem_open to return NULL (2025-08-11 23:01:00 -0700)

----------------------------------------------------------------
12 hotfixes.  5 are cc:stable and the remainder address post-6.16 issues
or aren't considered necessary for -stable kernels.  10 of these fixes are
for MM.

----------------------------------------------------------------
Barry Song (1):
      mm: fix the race between collapse and PT_RECLAIM under per-vma lock

Breno Leitao (1):
      mm/kmemleak: avoid deadlock by moving pr_warn() outside kmemleak_lock

Dev Jain (1):
      mm: pass page directly instead of using folio_page

Jann Horn (1):
      kasan/test: fix protection against compiler elision

Jialin Wang (1):
      proc: proc_maps_open allow proc_mem_open to return NULL

Jinjiang Tu (2):
      mm/smaps: fix race between smaps_hugetlb_range and migration
      fs/proc/task_mmu: hold PTL in pagemap_hugetlb_range and gather_hugetlb_stats

Lorenzo Stoakes (1):
      mm/mremap: avoid expensive folio lookup on mremap folio pte batch

Masami Hiramatsu (Google) (1):
      MAINTAINERS: add Masami as a reviewer of hung task detector

Sukrut Heroorkar (1):
      selftests/proc: fix string literal warning in proc-maps-race.c

Suren Baghdasaryan (1):
      userfaultfd: fix a crash in UFFDIO_MOVE when PMD is a migration entry

Waiman Long (1):
      mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()

 MAINTAINERS                                   |  1 +
 fs/proc/task_mmu.c                            | 24 ++++++++++++++++++------
 mm/kasan/kasan_test_c.c                       |  2 +-
 mm/khugepaged.c                               |  2 +-
 mm/kmemleak.c                                 | 10 +++++++++-
 mm/mprotect.c                                 | 23 ++++++++++-------------
 mm/mremap.c                                   |  4 ++++
 mm/userfaultfd.c                              | 17 ++++++++++-------
 tools/testing/selftests/proc/proc-maps-race.c |  6 +++---
 9 files changed, 57 insertions(+), 32 deletions(-)



             reply	other threads:[~2025-08-13  3:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13  3:52 Andrew Morton [this message]
2025-08-13 15:42 ` 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=20250812205256.7782e2e483a8b12774e65dcd@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@linux-foundation.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