[v5.15] INFO: task hung in gfs2_create_inode
0 views
Skip to first unread message
syzbot
12:57 AM (15 hours ago) 12:57 AM
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d848f2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=da57ab096137fd13d2f9
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+da57ab...@syzkaller.appspotmail.com
INFO: task syz.0.80:4702 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.80 state:D stack:24632 pid: 4702 ppid: 4187 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
bit_wait+0xd/0xc0 kernel/sched/wait_bit.c:199
__wait_on_bit kernel/sched/wait_bit.c:49 [inline]
out_of_line_wait_on_bit+0x173/0x230 kernel/sched/wait_bit.c:64
wait_on_bit include/linux/wait_bit.h:76 [inline]
gfs2_glock_wait+0xd9/0x1c0 fs/gfs2/glock.c:1282
gfs2_glock_nq_init fs/gfs2/glock.h:246 [inline]
gfs2_create_inode+0x2a4/0x1460 fs/gfs2/inode.c:629
gfs2_mkdir+0x9b/0xd0 fs/gfs2/inode.c:1238
vfs_mkdir+0x387/0x570 fs/namei.c:4073
do_mkdirat+0x1df/0x5b0 fs/namei.c:4098
__do_sys_mkdirat fs/namei.c:4113 [inline]
__se_sys_mkdirat fs/namei.c:4111 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4111
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fdd5fd92819
RSP: 002b:00007fdd5dfec028 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fdd6000bfa0 RCX: 00007fdd5fd92819
RDX: 000000000000004c RSI: 00002000000000c0 RDI: ffffffffffffff9c
RBP: 00007fdd5fe28c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fdd6000c038 R14: 00007fdd6000bfa0 R15: 00007ffca37db5a8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c31eaa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/1:2/1108:
#0: ffff888140fb9938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
#1: ffffc90004757d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
#2: ffff8881486be220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#2: ffff8881486be220 (&dev->mutex){....}-{3:3}, at: hub_event+0x19f/0x55e0 drivers/usb/core/hub.c:5827
#3: ffff88805ed3d220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#3: ffff88805ed3d220 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:954
#4: ffff8880187a61a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#4: ffff8880187a61a8 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:954
1 lock held by udevd/3562:
#0: ffff8880b903a358 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
2 locks held by getty/3946:
#0: ffff88814d310098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900025e62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5df/0x1a70 drivers/tty/n_tty.c:2158
1 lock held by syz-executor/4188:
#0: ffffffff8c323528 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#0: ffffffff8c323528 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2d1/0x750 kernel/rcu/tree_exp.h:845
2 locks held by kworker/u4:7/4300:
2 locks held by kworker/0:19/4527:
#0: ffff888016c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
#1: ffffc90003387d00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
2 locks held by syz.0.80/4702:
#0: ffff888058308460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386
#1: ffff88805f958150 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
#1: ffff88805f958150 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: filename_create+0x208/0x470 fs/namei.c:3843
4 locks held by udevd/4724:
#0: ffff88807d38b2f0 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xad/0xd50 fs/seq_file.c:182
#1: ffff88805e59e088 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x51/0x3c0 fs/kernfs/file.c:112
#2: ffff888052a321d8 (kn->active#32){++++}-{0:0}, at: kernfs_seq_start+0x71/0x3c0 fs/kernfs/file.c:113
#3: ffff88805ed3d220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#3: ffff88805ed3d220 (&dev->mutex){....}-{3:3}, at: uevent_show+0x17a/0x330 drivers/base/core.c:2408
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4188 Comm: syz-executor Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
RIP: 0010:orc_ip arch/x86/kernel/unwind_orc.c:30 [inline]
RIP: 0010:__orc_find arch/x86/kernel/unwind_orc.c:52 [inline]
RIP: 0010:orc_find arch/x86/kernel/unwind_orc.c:178 [inline]
RIP: 0010:unwind_next_frame+0x105e/0x1d90 arch/x86/kernel/unwind_orc.c:448
Code: c1 48 c1 f9 02 48 c1 e8 3f 48 01 c8 48 83 e0 fe 4d 8d 74 45 00 4c 89 f0 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df 0f b6 04 08 <84> c0 75 27 49 63 06 4c 01 f0 49 8d 4e 04 48 39 e8 4c 0f 46 e9 49
RSP: 0018:ffffc90002f6f1a8 EFLAGS: 00000a03
RAX: 0000000000000000 RBX: ffffc90002f6f268 RCX: dffffc0000000000
RDX: ffffffff8d9a8d00 RSI: ffffffff8e074780 RDI: ffffffff81350d2c
RBP: ffffffff81674dad R08: 0000000000000005 R09: 000000000000000e
R10: dffffc0000000000 R11: fffff520005ede59 R12: ffffffff8d9a8d10
R13: ffffffff8d9a8d0c R14: ffffffff8d9a8d0c R15: ffffffff8d9a8d08
FS: 000055556ee9d500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb82f4352f8 CR3: 0000000062b27000 CR4: 00000000003506f0
DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002
DR3: ffffffffefffff15 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
arch_stack_walk+0x10c/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0xa6/0xf0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd5/0x110 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1710 [inline]
slab_free_freelist_hook+0xea/0x170 mm/slub.c:1736
slab_free mm/slub.c:3504 [inline]
kfree+0xef/0x2a0 mm/slub.c:4564
f2fs_destroy_node_manager+0xcfe/0xf60 fs/f2fs/node.c:3400
f2fs_put_super+0x78a/0xcb0 fs/f2fs/super.c:1644
generic_shutdown_super+0x130/0x300 fs/super.c:475
kill_block_super+0x7c/0xe0 fs/super.c:1427
kill_f2fs_super+0x309/0x3c0 fs/f2fs/super.c:4568
deactivate_locked_super+0x93/0xf0 fs/super.c:335
cleanup_mnt+0x42d/0x4e0 fs/namespace.c:1148
task_work_run+0x125/0x1a0 kernel/task_work.c:188
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f5b3915fa57
Code: a2 c7 05 9c fc 24 00 00 00 00 00 eb 96 e8 e1 12 00 00 90 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 e8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffd06a60688 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f5b391f4048 RCX: 00007f5b3915fa57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffd06a60740
RBP: 00007ffd06a60740 R08: 00007ffd06a61740 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd06a617d0
R13: 00007f5b391f4048 R14: 000000000003c6dc R15: 00007ffd06a61810
</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 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 found the following issue on:
HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d848f2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=da57ab096137fd13d2f9
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+da57ab...@syzkaller.appspotmail.com
INFO: task syz.0.80:4702 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.80 state:D stack:24632 pid: 4702 ppid: 4187 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11ef/0x43c0 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
bit_wait+0xd/0xc0 kernel/sched/wait_bit.c:199
__wait_on_bit kernel/sched/wait_bit.c:49 [inline]
out_of_line_wait_on_bit+0x173/0x230 kernel/sched/wait_bit.c:64
wait_on_bit include/linux/wait_bit.h:76 [inline]
gfs2_glock_wait+0xd9/0x1c0 fs/gfs2/glock.c:1282
gfs2_glock_nq_init fs/gfs2/glock.h:246 [inline]
gfs2_create_inode+0x2a4/0x1460 fs/gfs2/inode.c:629
gfs2_mkdir+0x9b/0xd0 fs/gfs2/inode.c:1238
vfs_mkdir+0x387/0x570 fs/namei.c:4073
do_mkdirat+0x1df/0x5b0 fs/namei.c:4098
__do_sys_mkdirat fs/namei.c:4113 [inline]
__se_sys_mkdirat fs/namei.c:4111 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4111
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fdd5fd92819
RSP: 002b:00007fdd5dfec028 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fdd6000bfa0 RCX: 00007fdd5fd92819
RDX: 000000000000004c RSI: 00002000000000c0 RDI: ffffffffffffff9c
RBP: 00007fdd5fe28c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fdd6000c038 R14: 00007fdd6000bfa0 R15: 00007ffca37db5a8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c31eaa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/1:2/1108:
#0: ffff888140fb9938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
#1: ffffc90004757d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
#2: ffff8881486be220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#2: ffff8881486be220 (&dev->mutex){....}-{3:3}, at: hub_event+0x19f/0x55e0 drivers/usb/core/hub.c:5827
#3: ffff88805ed3d220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#3: ffff88805ed3d220 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:954
#4: ffff8880187a61a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#4: ffff8880187a61a8 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x480 drivers/base/dd.c:954
1 lock held by udevd/3562:
#0: ffff8880b903a358 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
2 locks held by getty/3946:
#0: ffff88814d310098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900025e62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5df/0x1a70 drivers/tty/n_tty.c:2158
1 lock held by syz-executor/4188:
#0: ffffffff8c323528 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#0: ffffffff8c323528 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2d1/0x750 kernel/rcu/tree_exp.h:845
2 locks held by kworker/u4:7/4300:
2 locks held by kworker/0:19/4527:
#0: ffff888016c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1
#1: ffffc90003387d00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285
2 locks held by syz.0.80/4702:
#0: ffff888058308460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386
#1: ffff88805f958150 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
#1: ffff88805f958150 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: filename_create+0x208/0x470 fs/namei.c:3843
4 locks held by udevd/4724:
#0: ffff88807d38b2f0 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xad/0xd50 fs/seq_file.c:182
#1: ffff88805e59e088 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x51/0x3c0 fs/kernfs/file.c:112
#2: ffff888052a321d8 (kn->active#32){++++}-{0:0}, at: kernfs_seq_start+0x71/0x3c0 fs/kernfs/file.c:113
#3: ffff88805ed3d220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#3: ffff88805ed3d220 (&dev->mutex){....}-{3:3}, at: uevent_show+0x17a/0x330 drivers/base/core.c:2408
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4188 Comm: syz-executor Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
RIP: 0010:orc_ip arch/x86/kernel/unwind_orc.c:30 [inline]
RIP: 0010:__orc_find arch/x86/kernel/unwind_orc.c:52 [inline]
RIP: 0010:orc_find arch/x86/kernel/unwind_orc.c:178 [inline]
RIP: 0010:unwind_next_frame+0x105e/0x1d90 arch/x86/kernel/unwind_orc.c:448
Code: c1 48 c1 f9 02 48 c1 e8 3f 48 01 c8 48 83 e0 fe 4d 8d 74 45 00 4c 89 f0 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df 0f b6 04 08 <84> c0 75 27 49 63 06 4c 01 f0 49 8d 4e 04 48 39 e8 4c 0f 46 e9 49
RSP: 0018:ffffc90002f6f1a8 EFLAGS: 00000a03
RAX: 0000000000000000 RBX: ffffc90002f6f268 RCX: dffffc0000000000
RDX: ffffffff8d9a8d00 RSI: ffffffff8e074780 RDI: ffffffff81350d2c
RBP: ffffffff81674dad R08: 0000000000000005 R09: 000000000000000e
R10: dffffc0000000000 R11: fffff520005ede59 R12: ffffffff8d9a8d10
R13: ffffffff8d9a8d0c R14: ffffffff8d9a8d0c R15: ffffffff8d9a8d08
FS: 000055556ee9d500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb82f4352f8 CR3: 0000000062b27000 CR4: 00000000003506f0
DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002
DR3: ffffffffefffff15 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
arch_stack_walk+0x10c/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0xa6/0xf0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd5/0x110 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1710 [inline]
slab_free_freelist_hook+0xea/0x170 mm/slub.c:1736
slab_free mm/slub.c:3504 [inline]
kfree+0xef/0x2a0 mm/slub.c:4564
f2fs_destroy_node_manager+0xcfe/0xf60 fs/f2fs/node.c:3400
f2fs_put_super+0x78a/0xcb0 fs/f2fs/super.c:1644
generic_shutdown_super+0x130/0x300 fs/super.c:475
kill_block_super+0x7c/0xe0 fs/super.c:1427
kill_f2fs_super+0x309/0x3c0 fs/f2fs/super.c:4568
deactivate_locked_super+0x93/0xf0 fs/super.c:335
cleanup_mnt+0x42d/0x4e0 fs/namespace.c:1148
task_work_run+0x125/0x1a0 kernel/task_work.c:188
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f5b3915fa57
Code: a2 c7 05 9c fc 24 00 00 00 00 00 eb 96 e8 e1 12 00 00 90 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 e8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffd06a60688 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f5b391f4048 RCX: 00007f5b3915fa57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffd06a60740
RBP: 00007ffd06a60740 R08: 00007ffd06a61740 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd06a617d0
R13: 00007f5b391f4048 R14: 000000000003c6dc R15: 00007ffd06a61810
</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 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
Reply all
Reply to author
Forward
0 new messages