From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, yhong@link.cuhk.edu.hk,
linux-f2fs-devel@lists.sourceforge.net, stable@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: use global inline_xattr_slab instead of per-sb slab cache
Date: Tue, 11 Nov 2025 22:50:13 +0000 [thread overview]
Message-ID: <176290141374.3596344.17459931762153462182.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251021034856.739272-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 21 Oct 2025 11:48:56 +0800 you wrote:
> As Hong Yun reported in mailing list:
>
> loop7: detected capacity change from 0 to 131072
> ------------[ cut here ]------------
> kmem_cache of name 'f2fs_xattr_entry-7:7' already exists
> WARNING: CPU: 0 PID: 24426 at mm/slab_common.c:110 kmem_cache_sanity_check mm/slab_common.c:109 [inline]
> WARNING: CPU: 0 PID: 24426 at mm/slab_common.c:110 __kmem_cache_create_args+0xa6/0x320 mm/slab_common.c:307
> CPU: 0 UID: 0 PID: 24426 Comm: syz.7.1370 Not tainted 6.17.0-rc4 #1 PREEMPT(full)
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
> RIP: 0010:kmem_cache_sanity_check mm/slab_common.c:109 [inline]
> RIP: 0010:__kmem_cache_create_args+0xa6/0x320 mm/slab_common.c:307
> Call Trace:
> __kmem_cache_create include/linux/slab.h:353 [inline]
> f2fs_kmem_cache_create fs/f2fs/f2fs.h:2943 [inline]
> f2fs_init_xattr_caches+0xa5/0xe0 fs/f2fs/xattr.c:843
> f2fs_fill_super+0x1645/0x2620 fs/f2fs/super.c:4918
> get_tree_bdev_flags+0x1fb/0x260 fs/super.c:1692
> vfs_get_tree+0x43/0x140 fs/super.c:1815
> do_new_mount+0x201/0x550 fs/namespace.c:3808
> do_mount fs/namespace.c:4136 [inline]
> __do_sys_mount fs/namespace.c:4347 [inline]
> __se_sys_mount+0x298/0x2f0 fs/namespace.c:4324
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0x8e/0x3a0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: use global inline_xattr_slab instead of per-sb slab cache
https://git.kernel.org/jaegeuk/f2fs/c/670b676d8343
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2025-11-11 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 3:48 [f2fs-dev] [PATCH v2] f2fs: use global inline_xattr_slab instead of per-sb slab cache Chao Yu via Linux-f2fs-devel
2025-11-11 22:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
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=176290141374.3596344.17459931762153462182.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@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).