From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
mm-commits@vger.kernel.org
Subject: [GIT PULL] hotfixes for 6.1-rc1
Date: Tue, 11 Oct 2022 19:10:42 -0700 [thread overview]
Message-ID: <20221011191042.ff46a7531fb68d05da1d2530@linux-foundation.org> (raw)
Linus, please merge this small series of fixups.
The following changes since commit 1c8e2349f2d033f634d046063b704b2ca6c46972:
damon/sysfs: fix possible memleak on damon_sysfs_add_target (2022-09-30 18:46:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2022-10-11
for you to fetch changes up to d0d51a97063db4704a5ef6bc978dddab1636a306:
nilfs2: fix leak of nilfs_root in case of writer thread creation failure (2022-10-11 19:05:45 -0700)
----------------------------------------------------------------
Five hotfixes - three for nilfs2, two for MM. For are cc:stable, one is
not.
----------------------------------------------------------------
Baolin Wang (1):
mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page
Ryusuke Konishi (3):
nilfs2: fix use-after-free bug of struct nilfs_root
nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()
nilfs2: fix leak of nilfs_root in case of writer thread creation failure
SeongJae Park (1):
mm/damon/core: initialize damon_target->list in damon_new_target()
fs/nilfs2/inode.c | 19 ++++++++++++++++++-
fs/nilfs2/segment.c | 7 +++----
include/linux/hugetlb.h | 8 ++++----
mm/damon/core.c | 1 +
mm/gup.c | 14 +++++++++++++-
mm/hugetlb.c | 27 +++++++++++++--------------
6 files changed, 52 insertions(+), 24 deletions(-)
next reply other threads:[~2022-10-12 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 2:10 Andrew Morton [this message]
2022-10-12 18:29 ` 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=20221011191042.ff46a7531fb68d05da1d2530@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