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: mm-commits@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] hotfixes for 6.6-rc3
Date: Sat, 23 Sep 2023 10:35:30 -0700	[thread overview]
Message-ID: <20230923103530.4df4257fc2b80c97a52b55b6@linux-foundation.org> (raw)

Linus, please pull this batch of hotfixes, thanks.

The following changes since commit ce9ecca0238b140b88f43859b211c9fdfd8e5b70:

  Linux 6.6-rc2 (2023-09-17 14:40:24 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2023-09-23-10-31

for you to fetch changes up to fe4419801617514765974f3e796269bc512ad146:

  proc: nommu: fix empty /proc/<pid>/maps (2023-09-19 13:21:34 -0700)

----------------------------------------------------------------
13 hotfixes, 10 of which pertain to post-6.5 issues.  The other 3 are
cc:stable.

----------------------------------------------------------------
Alexey Dobriyan (1):
      selftests/proc: fixup proc-empty-vm test after KSM changes

Andrew Morton (1):
      revert "scripts/gdb/symbols: add specific ko module load command"

Ben Wolsieffer (2):
      proc: nommu: /proc/<pid>/maps: release mmap read lock
      proc: nommu: fix empty /proc/<pid>/maps

Geert Uytterhoeven (1):
      sh: mm: re-add lost __ref to ioremap_prot() to fix modpost warning

Jens Axboe (1):
      task_work: add kerneldoc annotation for 'data' argument

Johannes Weiner (2):
      mm: page_alloc: fix CMA and HIGHATOMIC landing on the wrong buddy list
      mm: memcontrol: fix GFP_NOFS recursion in memory.high enforcement

Randy Dunlap (3):
      scatterlist: add missing function params to kernel-doc
      argv_split: fix kernel-doc warnings
      pidfd: prevent a kernel-doc warning

Ryan Roberts (1):
      selftests: link libasan statically for tests with -fsanitize=address

Yin Fengwei (1):
      filemap: add filemap_map_order0_folio() to handle order0 folio

 arch/sh/mm/ioremap.c                         |  4 +-
 fs/proc/internal.h                           |  2 -
 fs/proc/task_nommu.c                         | 64 +++++++++++++++-----------
 include/linux/memcontrol.h                   |  4 +-
 include/linux/resume_user_mode.h             |  2 +-
 kernel/pid.c                                 |  2 +-
 kernel/task_work.c                           |  1 +
 lib/argv_split.c                             |  4 +-
 lib/scatterlist.c                            |  4 +-
 mm/filemap.c                                 | 69 +++++++++++++++++++---------
 mm/memcontrol.c                              |  6 +--
 mm/page_alloc.c                              | 12 ++---
 scripts/gdb/linux/symbols.py                 | 23 +---------
 tools/testing/selftests/fchmodat2/Makefile   |  2 +-
 tools/testing/selftests/openat2/Makefile     |  2 +-
 tools/testing/selftests/proc/proc-empty-vm.c |  1 +
 16 files changed, 111 insertions(+), 91 deletions(-)



             reply	other threads:[~2023-09-23 17:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 17:35 Andrew Morton [this message]
2023-09-23 19:08 ` 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=20230923103530.4df4257fc2b80c97a52b55b6@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