[moderation] [mm?] [cgroups?] kernel panic: stack is corrupted in lock_acquire (4)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 48f506ad0b68 Merge tag 'soc-fixes-6.13-2' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13439f30580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a2b862bf4a5409f
dashboard link: https://syzkaller.appspot.com/bug?extid=5b0649b647bf72f815b9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org cgr...@vger.kernel.org han...@cmpxchg.org linux-...@vger.kernel.org linu...@kvack.org mho...@kernel.org muchu...@linux.dev roman.g...@linux.dev shakee...@linux.dev]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-48f506ad.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/263edab20c8c/vmlinux-48f506ad.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b84eb39f0355/bzImage-48f506ad.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5b0649...@syzkaller.appspotmail.com

No such timeout policy "syz0"
loop0: detected capacity change from 0 to 4096
ntfs3(loop0): Different NTFS sector size (1024) and media sector size (512).
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_acquire+0x53e/0x550
CPU: 0 UID: 0 PID: 5317 Comm: syz.0.0 Not tainted 6.13.0-rc3-syzkaller-00289-g48f506ad0b68 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
panic+0x349/0x880 kernel/panic.c:354
__stack_chk_fail+0x15/0x20 kernel/panic.c:836
lock_acquire+0x53e/0x550
rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
rcu_read_lock include/linux/rcupdate.h:849 [inline]
percpu_ref_tryget_many include/linux/percpu-refcount.h:241 [inline]
percpu_ref_tryget+0x31/0x180 include/linux/percpu-refcount.h:266
css_tryget include/linux/cgroup_refcnt.h:45 [inline]
get_mem_cgroup_from_mm+0x103/0x2a0 mm/memcontrol.c:948
__mem_cgroup_charge+0x16/0x80 mm/memcontrol.c:4511
mem_cgroup_charge include/linux/memcontrol.h:646 [inline]
filemap_add_folio+0xb7/0x380 mm/filemap.c:966
do_read_cache_folio+0x349/0x5b0 mm/filemap.c:3793
do_read_cache_page mm/filemap.c:3892 [inline]
read_cache_page+0x5b/0x170 mm/filemap.c:3901
read_mapping_page include/linux/pagemap.h:1005 [inline]
inode_read_data+0x85/0x450 fs/ntfs3/inode.c:1074
ntfs_fill_super+0x3f29/0x4730 fs/ntfs3/super.c:1491
get_tree_bdev_flags+0x48c/0x5c0 fs/super.c:1636
vfs_get_tree+0x90/0x2b0 fs/super.c:1814
do_new_mount+0x2be/0xb40 fs/namespace.c:3507
do_mount fs/namespace.c:3847 [inline]
__do_sys_mount fs/namespace.c:4057 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4034
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f974b5874ca
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f974affde68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f974affdef0 RCX: 00007f974b5874ca
RDX: 000000002001f800 RSI: 000000002001f840 RDI: 00007f974affdeb0
RBP: 000000002001f800 R08: 00007f974affdef0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000002001f840
R13: 00007f974affdeb0 R14: 000000000001f7f9 R15: 000000002001f880
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.