All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Ted Tso <tytso@mit.edu>
Cc: <linux-ext4@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	Jan Kara <jack@suse.cz>
Subject: [PATCH v3 01/12] ext4: Handle redirtying in ext4_bio_write_page()
Date: Mon,  5 Dec 2022 13:29:15 +0100	[thread overview]
Message-ID: <20221205122928.21959-1-jack@suse.cz> (raw)
In-Reply-To: <20221205122604.25994-1-jack@suse.cz>

Since we want to transition transaction commits to use ext4_writepages()
for writing back ordered, add handling of page redirtying into
ext4_bio_write_page(). Also move buffer dirty bit clearing into the same
place other buffer state handling.

Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
Signed-off-by: Jan Kara <jack@suse.cz>
---
 fs/ext4/page-io.c | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

diff --git a/fs/ext4/page-io.c b/fs/ext4/page-io.c
index 97fa7b4c645f..4e68ace86f11 100644
--- a/fs/ext4/page-io.c
+++ b/fs/ext4/page-io.c
@@ -482,6 +482,13 @@ int ext4_bio_write_page(struct ext4_io_submit *io,
 			/* A hole? We can safely clear the dirty bit */
 			if (!buffer_mapped(bh))
 				clear_buffer_dirty(bh);
+			/*
+			 * Keeping dirty some buffer we cannot write? Make
+			 * sure to redirty the page. This happens e.g. when
+			 * doing writeout for transaction commit.
+			 */
+			if (buffer_dirty(bh) && !PageDirty(page))
+				redirty_page_for_writepage(wbc, page);
 			if (io->io_bio)
 				ext4_io_submit(io);
 			continue;
@@ -489,6 +496,7 @@ int ext4_bio_write_page(struct ext4_io_submit *io,
 		if (buffer_new(bh))
 			clear_buffer_new(bh);
 		set_buffer_async_write(bh);
+		clear_buffer_dirty(bh);
 		nr_to_submit++;
 	} while ((bh = bh->b_this_page) != head);
 
@@ -532,7 +540,10 @@ int ext4_bio_write_page(struct ext4_io_submit *io,
 			printk_ratelimited(KERN_ERR "%s: ret = %d\n", __func__, ret);
 			redirty_page_for_writepage(wbc, page);
 			do {
-				clear_buffer_async_write(bh);
+				if (buffer_async_write(bh)) {
+					clear_buffer_async_write(bh);
+					set_buffer_dirty(bh);
+				}
 				bh = bh->b_this_page;
 			} while (bh != head);
 			goto unlock;
@@ -546,7 +557,6 @@ int ext4_bio_write_page(struct ext4_io_submit *io,
 		io_submit_add_bh(io, inode,
 				 bounce_page ? bounce_page : page, bh);
 		nr_submitted++;
-		clear_buffer_dirty(bh);
 	} while ((bh = bh->b_this_page) != head);
 
 unlock:
-- 
2.35.3


  reply	other threads:[~2022-12-05 12:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 12:29 [PATCH v3 0/12] ext4: Stop using ext4_writepage() for writeout of ordered data Jan Kara
2022-12-05 12:29 ` Jan Kara [this message]
2022-12-05 12:29 ` [PATCH v3 02/12] ext4: Move keep_towrite handling to ext4_bio_write_page() Jan Kara
2022-12-05 12:29 ` [PATCH v3 03/12] ext4: Remove nr_submitted from ext4_bio_write_page() Jan Kara
2022-12-05 12:29 ` [PATCH v3 04/12] ext4: Drop pointless IO submission " Jan Kara
2022-12-05 12:29 ` [PATCH v3 05/12] ext4: Add support for writepages calls that cannot map blocks Jan Kara
2022-12-05 12:29 ` [PATCH v3 06/12] ext4: Provide ext4_do_writepages() Jan Kara
2022-12-05 12:29 ` [PATCH v3 07/12] ext4: Move percpu_rwsem protection into ext4_writepages() Jan Kara
2022-12-05 12:29 ` [PATCH v3 08/12] ext4: Switch to using ext4_do_writepages() for ordered data writeout Jan Kara
2022-12-05 12:29 ` [PATCH v3 09/12] jbd2: Switch jbd2_submit_inode_data() to use fs-provided hook for " Jan Kara
2022-12-05 12:29 ` [PATCH v3 10/12] ext4: Switch to using write_cache_pages() for data=journal writeout Jan Kara
2022-12-05 12:29 ` [PATCH v3 11/12] ext4: Stop providing .writepage hook Jan Kara
2022-12-05 18:32   ` kernel test robot
2022-12-06  3:17   ` Theodore Ts'o
2022-12-06 10:52     ` Jan Kara
2022-12-07  7:38       ` Christoph Hellwig
2022-12-07 11:17         ` Jan Kara
2022-12-05 12:29 ` [PATCH v3 12/12] ext4: Remove ordered data support from ext4_writepage() Jan Kara

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=20221205122928.21959-1-jack@suse.cz \
    --to=jack@suse.cz \
    --cc=hch@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ritesh.list@gmail.com \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.