linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: "HONG, Yun" <yhong@link.cuhk.edu.hk>,
	"jaegeuk@kernel.org" <jaegeuk@kernel.org>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [Crash Report] WARNING in f2fs_init_xattr_caches
Date: Fri, 10 Oct 2025 15:16:54 +0800	[thread overview]
Message-ID: <1d8031b5-34c5-4d2f-8a70-b5055621380a@kernel.org> (raw)
In-Reply-To: <TYCP286MB3686D500C8AF350E0BE8B4F2C11BA@TYCP286MB3686.JPNP286.PROD.OUTLOOK.COM>

Hi Hong,

On 9/29/25 19:43, HONG, Yun wrote:
> Hi,
> 
> I would like to kindly report a crash I encountered, identified as "WARNING in f2fs_init_xattr_caches". This issue can be reproduced with a Syzlang reproducer on the mainline version downloaded from https://www.kernel.org/
> For your convenience, I have included a sample crash report, the configuration file, and a reproduction program as attachments.

Thank you for the report!

I tried attached repro.syz & config.txt, however, I can not reproduce the bug.

If you can reproduce this bug, could you please help to reproduce w/ debug
patch as below? and dump full log once it reproduces.

From: Chao Yu <chao@kernel.org>
Subject: [PATCH] f2fs: add debug log

---
 fs/f2fs/xattr.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/fs/f2fs/xattr.c b/fs/f2fs/xattr.c
index 58632a2b6613..81f591a45b41 100644
--- a/fs/f2fs/xattr.c
+++ b/fs/f2fs/xattr.c
@@ -845,10 +845,18 @@ int f2fs_init_xattr_caches(struct f2fs_sb_info *sbi)
 	if (!sbi->inline_xattr_slab)
 		return -ENOMEM;

+	printk("%s: slab_name: %s, %u:%u, %p\n", __func__, slab_name,
+				MAJOR(dev), MINOR(dev), sbi->inline_xattr_slab);
+
 	return 0;
 }

 void f2fs_destroy_xattr_caches(struct f2fs_sb_info *sbi)
 {
+	dev_t dev = sbi->sb->s_bdev->bd_dev;
+
+	printk("%s: %u:%u %p\n", __func__, MAJOR(dev), MINOR(dev),
+						sbi->inline_xattr_slab);
+
 	kmem_cache_destroy(sbi->inline_xattr_slab);
 }
-- 
2.49.0

Thanks,


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

       reply	other threads:[~2025-10-10  7:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <TYCP286MB3686D500C8AF350E0BE8B4F2C11BA@TYCP286MB3686.JPNP286.PROD.OUTLOOK.COM>
2025-10-10  7:16 ` Chao Yu via Linux-f2fs-devel [this message]
2025-10-13 12:17 ` [f2fs-dev] [Crash Report] WARNING in f2fs_init_xattr_caches Chao Yu via Linux-f2fs-devel
     [not found]   ` <TYCP286MB3686EE4EFAC2B76E2812C9B0C1EBA@TYCP286MB3686.JPNP286.PROD.OUTLOOK.COM>
2025-10-14  7:30     ` 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=1d8031b5-34c5-4d2f-8a70-b5055621380a@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=yhong@link.cuhk.edu.hk \
    /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).