From: Jan Kara <jack@suse.cz>
To: <linux-fsdevel@vger.kernel.org>
Cc: <linux-mm@kvack.org>, Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Mikhail Rudenko <xyzzy@yandex-team.ru>, Jan Kara <jack@suse.cz>
Subject: [PATCH v2 5/5] ext4: Defer inode reclaim if it has preallocations
Date: Fri, 11 Sep 2026 10:51:41 +0200 [thread overview]
Message-ID: <20260911085142.1774803-10-jack@suse.cz> (raw)
In-Reply-To: <20260911081309.14137-1-jack@suse.cz>
When we have to free preallocations during inode eviction, we need to
load block bitmaps and run transaction to modify them. This takes time
and also requires GFP_NOFAIL allocations. Mark inodes with preallocated
blocks as needing offloading of inode reclaim to a workqueue so that we
don't block reclaim for long and potentially deadlock MM subsystem.
Signed-off-by: Jan Kara <jack@suse.cz>
---
fs/ext4/mballoc.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 06171a11db12..4891f252105e 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -3115,6 +3115,13 @@ ext4_mb_regular_allocator(struct ext4_allocation_context *ac)
if (ac->ac_prefetch_nr)
ext4_mb_prefetch_fini(sb, ac->ac_prefetch_grp, ac->ac_prefetch_nr);
+ /*
+ * Freeing preallocations requires loading bitmaps and running
+ * transactions. Defer inode reclaim to a workqueue.
+ */
+ if (!RB_EMPTY_ROOT(&EXT4_I(ac->ac_inode)->i_prealloc_node))
+ mark_inode_reclaim_deferred(ac->ac_inode);
+
return err;
}
--
2.51.0
next prev parent reply other threads:[~2026-09-11 8:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 8:51 [PATCH 0/5 v2] fs: Deferred inode reclaim Jan Kara
2026-09-11 8:51 ` [PATCH v2 1/5] writeback: Fix missed lazytime flush Jan Kara
2026-09-11 8:51 ` [PATCH v2 2/5] fs: Avoid inode dirtying on last iput Jan Kara
2026-09-11 8:51 ` [PATCH v2 3/5] fs: Basic infrastructure for offloading inode reclaim Jan Kara
2026-09-11 8:51 ` [PATCH v2 4/5] fs: Add throttling to deferred " Jan Kara
2026-09-23 21:24 ` Andreas Gruenbacher
2026-09-24 17:09 ` Jan Kara
2026-09-29 21:10 ` Andreas Gruenbacher
2026-09-11 8:51 ` Jan Kara [this message]
2026-09-11 14:55 ` [PATCH 0/5 v2] fs: Deferred " Theodore Tso
2026-09-11 15:05 ` Darrick J. Wong
2026-09-17 9:56 ` Christian Brauner
2026-09-24 17:24 ` Jan Kara
2026-09-26 2:48 ` [PATCH v2 0/5] " Matthias Goergens
2026-09-29 10:37 ` Jan Kara
2026-09-30 10:18 ` Amir Goldstein
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=20260911085142.1774803-10-jack@suse.cz \
--to=jack@suse.cz \
--cc=brauner@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xyzzy@yandex-team.ru \
/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.