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.10-rc7
Date: Wed, 3 Jul 2024 22:27:28 -0700 [thread overview]
Message-ID: <20240703222728.d5ef62a48ebf19260832ee73@linux-foundation.org> (raw)
Linus, please merge this batch of hotfixes, thanks.
The following changes since commit 22a40d14b572deb80c0648557f4bd502d7e83826:
Linux 6.10-rc6 (2024-06-30 14:40:44 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm tags/mm-hotfixes-stable-2024-07-03-22-23
for you to fetch changes up to 93aef9eda1cea9e84ab2453fcceb8addad0e46f1:
nilfs2: fix incorrect inode allocation from reserved inodes (2024-07-03 12:29:25 -0700)
----------------------------------------------------------------
6 hotfies, all cc:stable. Some fixes for longstanding nilfs2 issues and
three unrelated MM fixes.
----------------------------------------------------------------
Jan Kara (2):
Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again"
mm: avoid overflows in dirty throttling logic
Jinliang Zheng (1):
mm: optimize the redundant loop of mm_update_owner_next()
Ryusuke Konishi (3):
nilfs2: fix inode number range checks
nilfs2: add missing check for inode numbers on directory entries
nilfs2: fix incorrect inode allocation from reserved inodes
fs/nilfs2/alloc.c | 19 +++++++++++++++----
fs/nilfs2/alloc.h | 4 ++--
fs/nilfs2/dat.c | 2 +-
fs/nilfs2/dir.c | 6 ++++++
fs/nilfs2/ifile.c | 7 ++-----
fs/nilfs2/nilfs.h | 10 ++++++++--
fs/nilfs2/the_nilfs.c | 6 ++++++
fs/nilfs2/the_nilfs.h | 2 +-
kernel/exit.c | 2 ++
mm/page-writeback.c | 32 +++++++++++++++++++++++++++-----
10 files changed, 70 insertions(+), 20 deletions(-)
next reply other threads:[~2024-07-04 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 5:27 Andrew Morton [this message]
2024-07-04 19:36 ` 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=20240703222728.d5ef62a48ebf19260832ee73@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