[<prev] [next>] [day] [month] [year] [list]
Message-ID: <690974be.050a0220.98a6.009b.GAE@google.com>
Date: Mon, 03 Nov 2025 19:36:30 -0800
From: syzbot <syzbot+cac5fae1f16b9bec64d3@...kaller.appspotmail.com>
To: almaz.alexandrovich@...agon-software.com, linux-kernel@...r.kernel.org,
ntfs3@...ts.linux.dev, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [ntfs3?] WARNING in generic_shutdown_super
Hello,
syzbot found the following issue on:
HEAD commit: 131f3d9446a6 Add linux-next specific files for 20251030
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=125cdf34580000
kernel config: https://syzkaller.appspot.com/x/.config?x=63d09725c93bcc1c
dashboard link: https://syzkaller.appspot.com/bug?extid=cac5fae1f16b9bec64d3
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4e9ddffcaef3/disk-131f3d94.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/da45f389fd4f/vmlinux-131f3d94.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f5312dd97449/bzImage-131f3d94.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+cac5fae1f16b9bec64d3@...kaller.appspotmail.com
------------[ cut here ]------------
WARNING: mm/slub.c:6762 at free_large_kmalloc+0x15c/0x1f0 mm/slub.c:6762, CPU#1: syz-executor/5826
Modules linked in:
CPU: 1 UID: 0 PID: 5826 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:free_large_kmalloc+0x15c/0x1f0 mm/slub.c:6762
Code: 44 89 f6 e8 16 d1 fc ff 65 48 8b 05 fe 06 58 10 48 3b 44 24 08 75 57 48 83 c4 10 5b 41 5c 41 5e 41 5f 5d c3 cc cc cc cc cc 90 <0f> 0b 90 65 48 8b 05 d9 06 58 10 48 3b 44 24 08 75 32 48 89 df 48
RSP: 0018:ffffc9000403fc88 EFLAGS: 00010206
RAX: 00000000ff000000 RBX: ffffea0000389080 RCX: ffffea0000389088
RDX: 0000000000000000 RSI: ffffffff8e2420e0 RDI: ffffea0000389080
RBP: 1ffff1100dd09d43 R08: ffffffff8f7d6777 R09: 1ffffffff1efacee
R10: dffffc0000000000 R11: fffffbfff1efacef R12: 1ffff1100dd09d36
R13: dffffc0000000000 R14: ffff88806e84e9b0 R15: ffff888078913308
FS: 0000555571060500(0000) GS:ffff888125fe5000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c3de4e1 CR3: 0000000078b0e000 CR4: 00000000003526f0
Call Trace:
<TASK>
generic_shutdown_super+0x135/0x2c0 fs/super.c:643
kill_block_super+0x44/0x90 fs/super.c:1723
ntfs3_kill_sb+0x44/0x1b0 fs/ntfs3/super.c:1847
deactivate_locked_super+0xbc/0x130 fs/super.c:474
cleanup_mnt+0x425/0x4c0 fs/namespace.c:1317
task_work_run+0x1d4/0x260 kernel/task_work.c:227
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop+0xe9/0x130 kernel/entry/common.c:43
exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline]
do_syscall_64+0x2bd/0xfa0 arch/x86/entry/syscall_64.c:100
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9b943902f7
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc6a8bafa8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f9b94411d7d RCX: 00007f9b943902f7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffc6a8bb060
RBP: 00007ffc6a8bb060 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffc6a8bc0f0
R13: 00007f9b94411d7d R14: 000000000001c88b R15: 00007ffc6a8bc130
</TASK>
---
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 syzkaller@...glegroups.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
Powered by blists - more mailing lists