Linux-f2fs-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH v4 10/12] f2fs: cache: support fault injection
Date: Thu, 27 Aug 2026 20:25:38 +0800	[thread overview]
Message-ID: <20260827122541.19967-11-chao@kernel.org> (raw)
In-Reply-To: <20260827122541.19967-1-chao@kernel.org>

From: Chao Yu <chao@kernel.org>

This patch adds fault injection support for metadata cache allocations
to improve error-path test coverage.
- it integrates entry allocations with FAULT_KALLOC

Signed-off-by: Chao Yu <chao@kernel.org>
---
 fs/f2fs/cache.c | 24 ++++++++++++++----------
 1 file changed, 14 insertions(+), 10 deletions(-)

diff --git a/fs/f2fs/cache.c b/fs/f2fs/cache.c
index 058e62c44152..2a98479bb3db 100644
--- a/fs/f2fs/cache.c
+++ b/fs/f2fs/cache.c
@@ -176,23 +176,27 @@ static struct f2fs_cached_block *f2fs_create_cache(
 		struct f2fs_cached_block_list *cache,
 		unsigned long index, bool nofail)
 {
+	struct f2fs_sb_info *sbi = cache->sbi;
 	struct f2fs_cached_block *entry;
 	unsigned int flags = GFP_NOFS;
 
 	if (index == ULONG_MAX)
 		return ERR_PTR(-ERANGE);
 
-	if (nofail)
+	if (nofail) {
 		flags |= __GFP_NOFAIL;
-
-	entry = kzalloc_obj(*entry, flags);
-	if (!entry)
-		return ERR_PTR(-ENOMEM);
-
-	entry->data = kmalloc(cache->sbi->blocksize, flags);
-	if (!entry->data) {
-		kfree(entry);
-		return ERR_PTR(-ENOMEM);
+		entry = kzalloc_obj(*entry, flags);
+		entry->data = kmalloc(sbi->blocksize, flags);
+	} else {
+		entry = f2fs_kzalloc(sbi, sizeof(*entry), flags);
+		if (!entry)
+			return ERR_PTR(-ENOMEM);
+
+		entry->data = f2fs_kmalloc(sbi, sbi->blocksize, flags);
+		if (!entry->data) {
+			kfree(entry);
+			return ERR_PTR(-ENOMEM);
+		}
 	}
 
 	entry->index = index;
-- 
2.49.0



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  parent reply	other threads:[~2026-08-27 12:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 12:25 [f2fs-dev] [PATCH v4 00/12] f2fs: introduce metadata cache Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 01/12] f2fs: cache: implement " Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 02/12] f2fs: cache: initialize meta cache Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 03/12] f2fs: cache: introduce shrinker Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 04/12] f2fs: cache: introduce writeback thread Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 05/12] f2fs: cache: use meta cache Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 06/12] f2fs: cache: initialize node cache Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 07/12] f2fs: cache: use " Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 08/12] f2fs: cache: initialize compress cache Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 09/12] f2fs: cache: use " Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` Chao Yu via Linux-f2fs-devel [this message]
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 11/12] f2fs: cache: introduce tracepoints Chao Yu via Linux-f2fs-devel
2026-08-27 12:25 ` [f2fs-dev] [PATCH v4 12/12] f2fs: cache: show per-cache usage in debugfs Chao Yu via Linux-f2fs-devel

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=20260827122541.19967-11-chao@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-kernel@vger.kernel.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