From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 2/4] gfs2: remove ->writepage
Date: Tue, 19 Jul 2022 06:13:09 +0200 [thread overview]
Message-ID: <20220719041311.709250-3-hch@lst.de> (raw)
In-Reply-To: <20220719041311.709250-1-hch@lst.de>
->writepage is only used for single page writeback from memory reclaim,
and not called at all for cgroup writeback. Follow the lead of XFS
and remove ->writepage and rely entirely on ->writepages.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Tested-by: Andreas Gruenbacher <agruenba@redhat.com>
Reviewed-by: Andreas Gruenbacher <agruenba@redhat.com>
---
fs/gfs2/aops.c | 26 --------------------------
1 file changed, 26 deletions(-)
diff --git a/fs/gfs2/aops.c b/fs/gfs2/aops.c
index 106e90a365838..0240a1a717f56 100644
--- a/fs/gfs2/aops.c
+++ b/fs/gfs2/aops.c
@@ -81,31 +81,6 @@ static int gfs2_get_block_noalloc(struct inode *inode, sector_t lblock,
return 0;
}
-/**
- * gfs2_writepage - Write page for writeback mappings
- * @page: The page
- * @wbc: The writeback control
- */
-static int gfs2_writepage(struct page *page, struct writeback_control *wbc)
-{
- struct inode *inode = page->mapping->host;
- struct gfs2_inode *ip = GFS2_I(inode);
- struct gfs2_sbd *sdp = GFS2_SB(inode);
- struct iomap_writepage_ctx wpc = { };
-
- if (gfs2_assert_withdraw(sdp, gfs2_glock_is_held_excl(ip->i_gl)))
- goto out;
- if (current->journal_info)
- goto redirty;
- return iomap_writepage(page, wbc, &wpc, &gfs2_writeback_ops);
-
-redirty:
- redirty_page_for_writepage(wbc, page);
-out:
- unlock_page(page);
- return 0;
-}
-
/**
* gfs2_write_jdata_page - gfs2 jdata-specific version of block_write_full_page
* @page: The page to write
@@ -765,7 +740,6 @@ bool gfs2_release_folio(struct folio *folio, gfp_t gfp_mask)
}
static const struct address_space_operations gfs2_aops = {
- .writepage = gfs2_writepage,
.writepages = gfs2_writepages,
.read_folio = gfs2_read_folio,
.readahead = gfs2_readahead,
--
2.30.2
next prev parent reply other threads:[~2022-07-19 4:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 4:13 [Cluster-devel] remove iomap_writepage v2 Christoph Hellwig
2022-07-19 4:13 ` [Cluster-devel] [PATCH 1/4] gfs2: stop using generic_writepages in gfs2_ail1_start_one Christoph Hellwig
2023-01-18 21:22 ` Andreas Gruenbacher
2023-01-19 6:22 ` Christoph Hellwig
2022-07-19 4:13 ` Christoph Hellwig [this message]
2022-07-19 4:13 ` [Cluster-devel] [PATCH 3/4] zonefs: remove ->writepage Christoph Hellwig
2022-07-19 6:56 ` Chaitanya Kulkarni
2022-07-19 4:13 ` [Cluster-devel] [PATCH 4/4] iomap: remove iomap_writepage Christoph Hellwig
2022-07-19 6:56 ` Chaitanya Kulkarni
2022-07-22 17:56 ` Darrick J. Wong
2022-07-28 11:10 ` [Cluster-devel] remove iomap_writepage v2 Jan Kara
2022-07-28 14:18 ` Matthew Wilcox
2022-07-28 22:48 ` Dave Chinner
2022-07-28 23:26 ` Yang Shi
2022-07-29 9:22 ` Mel Gorman
2022-07-29 14:11 ` Christoph Hellwig
2022-08-01 15:31 ` Johannes Weiner
2022-08-10 20:43 ` Matthew Wilcox
2022-08-10 21:32 ` Andreas Grünbacher
2022-08-10 23:17 ` Matthew Wilcox
2022-08-11 5:58 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2022-07-11 4:14 [Cluster-devel] remove iomap_writepage Christoph Hellwig
2022-07-11 4:14 ` [Cluster-devel] [PATCH 2/4] gfs2: remove ->writepage Christoph Hellwig
2022-07-11 23:22 ` Andreas Grünbacher
2022-07-12 4:57 ` Christoph Hellwig
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=20220719041311.709250-3-hch@lst.de \
--to=hch@lst.de \
/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;
as well as URLs for NNTP newsgroup(s).