From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Folio fixes for 5.19
Date: Fri, 10 Jun 2022 20:22:06 +0100 [thread overview]
Message-ID: <YqOZ3v68HrM9LI//@casper.infradead.org> (raw)
The following changes since commit 3d9f55c57bc3659f986acc421eac431ff6edcc83:
Merge tag 'fs_for_v5.19-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs (2022-06-09 12:26:05 -0700)
are available in the Git repository at:
git://git.infradead.org/users/willy/pagecache.git tags/folio-5.19a
for you to fetch changes up to 334f6f53abcf57782bd2fe81da1cbd893e4ef05c:
mm: Add kernel-doc for folio->mlock_count (2022-06-09 16:24:25 -0400)
----------------------------------------------------------------
Four folio-related fixes for 5.19:
- Don't release a folio while it's still locked
- Fix a use-after-free after dropping the mmap_lock
- Fix a memory leak when splitting a page
- Fix a kernel-doc warning for struct folio
----------------------------------------------------------------
Matthew Wilcox (Oracle) (4):
filemap: Don't release a locked folio
filemap: Cache the value of vm_flags
mm/huge_memory: Fix xarray node memory leak
mm: Add kernel-doc for folio->mlock_count
include/linux/mm_types.h | 5 +++++
include/linux/xarray.h | 1 +
lib/xarray.c | 5 +++--
mm/filemap.c | 9 +++++----
mm/huge_memory.c | 3 +--
mm/readahead.c | 2 ++
6 files changed, 17 insertions(+), 8 deletions(-)
next reply other threads:[~2022-06-10 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 19:22 Matthew Wilcox [this message]
2022-06-10 19:56 ` Linus Torvalds
2022-06-10 21:39 ` Matthew Wilcox
2022-06-10 23:27 ` Linus Torvalds
2022-06-10 19:58 ` 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=YqOZ3v68HrM9LI//@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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