From: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
To: linux-mm@kvack.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, akpm@linux-foundation.org,
willy@infradead.org, naoya.horiguchi@nec.com, tytso@mit.edu,
"Vishal Moola (Oracle)" <vishal.moola@gmail.com>
Subject: [PATCH v2 0/4] Removing the try_to_release_page() wrapper
Date: Thu, 17 Nov 2022 18:14:06 -0800 [thread overview]
Message-ID: <20221118021410.24420-1-vishal.moola@gmail.com> (raw)
This patchset replaces the remaining calls of try_to_release_page() with
the folio equivalent: filemap_release_folio(). This allows us to remove
the wrapper.
The set passes fstests on ext4 and xfs.
---
v2:
Added VM_BUG_ON_FOLIO to ext4 for catching future data corruption
Vishal Moola (Oracle) (4):
ext4: Convert move_extent_per_page() to use folios
khugepage: Replace try_to_release_page() with filemap_release_folio()
memory-failure: Convert truncate_error_page() to use folio
folio-compat: Remove try_to_release_page()
fs/ext4/move_extent.c | 52 ++++++++++++++++++++++++-----------------
include/linux/pagemap.h | 1 -
mm/folio-compat.c | 6 -----
mm/khugepaged.c | 23 +++++++++---------
mm/memory-failure.c | 5 ++--
5 files changed, 46 insertions(+), 41 deletions(-)
--
2.38.1
next reply other threads:[~2022-11-18 2:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 2:14 Vishal Moola (Oracle) [this message]
2022-11-18 2:14 ` [PATCH v2 1/4] ext4: Convert move_extent_per_page() to use folios Vishal Moola (Oracle)
2022-11-18 7:28 ` Vishal Moola
2022-11-18 2:14 ` [PATCH v2 2/4] khugepage: Replace try_to_release_page() with filemap_release_folio() Vishal Moola (Oracle)
2022-11-18 2:14 ` [PATCH v2 3/4] memory-failure: Convert truncate_error_page() to use folio Vishal Moola (Oracle)
2022-11-18 2:14 ` [PATCH v2 4/4] folio-compat: Remove try_to_release_page() Vishal Moola (Oracle)
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=20221118021410.24420-1-vishal.moola@gmail.com \
--to=vishal.moola@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=tytso@mit.edu \
--cc=willy@infradead.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