* [syzbot] INFO: task hung in __filemap_get_folio
@ 2022-08-08 8:05 syzbot
2022-09-10 7:06 ` syzbot
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: syzbot @ 2022-08-08 8:05 UTC (permalink / raw)
To: akpm, linux-fsdevel, linux-kernel, linux-mm, syzkaller-bugs, willy
Hello,
syzbot found the following issue on:
HEAD commit: ca688bff68bc Add linux-next specific files for 20220808
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16ebfe8e080000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c20e006003cdecb
dashboard link: https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0e9dc403e57033a74b1d@syzkaller.appspotmail.com
INFO: task syz-executor.1:19798 blocked for more than 147 seconds.
Not tainted 5.19.0-next-20220808-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1 state:D stack:26208 pid:19798 ppid:3629 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
io_schedule+0xba/0x130 kernel/sched/core.c:8714
folio_wait_bit_common+0x3dd/0xa90 mm/filemap.c:1298
__folio_lock mm/filemap.c:1664 [inline]
folio_lock include/linux/pagemap.h:939 [inline]
folio_lock include/linux/pagemap.h:935 [inline]
__filemap_get_folio+0xc6d/0xed0 mm/filemap.c:1936
truncate_inode_pages_range+0x37c/0x1510 mm/truncate.c:378
ntfs_evict_inode+0x16/0xa0 fs/ntfs3/inode.c:1741
evict+0x2ed/0x6b0 fs/inode.c:665
iput_final fs/inode.c:1748 [inline]
iput.part.0+0x55d/0x810 fs/inode.c:1774
iput+0x58/0x70 fs/inode.c:1764
ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f50d0c8a7aa
RSP: 002b:00007f50d1d0bf88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f50d0c8a7aa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f50d1d0bfe0
RBP: 00007f50d1d0c020 R08: 00007f50d1d0c020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f50d1d0bfe0 R15: 000000002007aa80
</TASK>
Showing all threads with locks held in the system:
task:rcu_tasks_kthre state:I stack:29000 pid:12 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
rcu_tasks_one_gp+0x3e5/0xc70 kernel/rcu/tasks.h:514
rcu_tasks_kthread+0x73/0xa0 kernel/rcu/tasks.h:552
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8bf889b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
task:rcu_tasks_trace state:I stack:29120 pid:13 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
rcu_tasks_one_gp+0x3e5/0xc70 kernel/rcu/tasks.h:514
rcu_tasks_kthread+0x73/0xa0 kernel/rcu/tasks.h:552
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8bf886b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
task:getty state:S stack:23392 pid:3288 ppid:1 flags:0x00000000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
schedule_timeout+0x1db/0x2a0 kernel/time/timer.c:1911
wait_woken+0x18b/0x1f0 kernel/sched/wait.c:459
n_tty_read+0x1051/0x13e0 drivers/tty/n_tty.c:2243
iterate_tty_read drivers/tty/tty_io.c:858 [inline]
tty_read+0x33a/0x5d0 drivers/tty/tty_io.c:933
call_read_iter include/linux/fs.h:2186 [inline]
new_sync_read fs/read_write.c:389 [inline]
vfs_read+0x67d/0x930 fs/read_write.c:470
ksys_read+0x127/0x250 fs/read_write.c:607
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7efd62c0e8fe
RSP: 002b:00007fff0e6822e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 000055bbf57e9910 RCX: 00007efd62c0e8fe
RDX: 0000000000000001 RSI: 00007fff0e682300 RDI: 0000000000000000
RBP: 000055bbf57e9970 R08: 0000000000000007 R09: 000055bbf57eacd0
R10: 0000000000000063 R11: 0000000000000246 R12: 000055bbf57e99ac
R13: 00007fff0e682300 R14: 0000000000000000 R15: 000055bbf57e99ac
</TASK>
2 locks held by getty/3288:
#0: ffff88814a08b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
#1: ffffc90002d232f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef0/0x13e0 drivers/tty/n_tty.c:2177
task:kworker/0:17 state:D stack:24880 pid:12659 ppid:2 flags:0x00004000
Workqueue: events key_garbage_collector
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
synchronize_rcu_expedited+0x39a/0x670 kernel/rcu/tree_exp.h:955
synchronize_rcu+0x2c3/0x370 kernel/rcu/tree.c:3519
key_garbage_collector+0x3bd/0x910 security/keys/gc.c:292
process_one_work+0x991/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
3 locks held by kworker/0:17/12659:
#0: ffff888011864d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
#0: ffff888011864d38 ((wq_completion)events){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
#0: ffff888011864d38 ((wq_completion)events){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1280 [inline]
#0: ffff888011864d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:636 [inline]
#0: ffff888011864d38 ((wq_completion)events){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:663 [inline]
#0: ffff888011864d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x87a/0x1610 kernel/workqueue.c:2260
#1: ffffc9000309fda8 (key_gc_work){+.+.}-{0:0}, at: process_one_work+0x8ae/0x1610 kernel/workqueue.c:2264
#2: ffffffff8bf941b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#2: ffffffff8bf941b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x562/0x670 kernel/rcu/tree_exp.h:940
task:kworker/u4:2 state:R running task stack:27208 pid:16592 ppid:2 flags:0x00004000
Workqueue: events_unbound flush_to_ldisc
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
pty_write_room drivers/tty/pty.c:133 [inline]
pty_write_room+0xb3/0xe0 drivers/tty/pty.c:129
</TASK>
no locks held by kworker/u4:2/16592.
task:kworker/0:9 state:D stack:25896 pid:19133 ppid:2 flags:0x00004000
Workqueue: rcu_gp wait_rcu_exp_gp
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
schedule_timeout+0x14a/0x2a0 kernel/time/timer.c:1935
synchronize_rcu_expedited_wait_once kernel/rcu/tree_exp.h:571 [inline]
synchronize_rcu_expedited_wait kernel/rcu/tree_exp.h:622 [inline]
rcu_exp_wait_wake+0x28f/0xf80 kernel/rcu/tree_exp.h:688
process_one_work+0x991/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
2 locks held by kworker/0:9/19133:
#0: ffff888011866538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline]
#0: ffff888011866538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: arch_atomic_long_set include/linux/atomic/atomic-long.h:41 [inline]
#0: ffff888011866538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: atomic_long_set include/linux/atomic/atomic-instrumented.h:1280 [inline]
#0: ffff888011866538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:636 [inline]
#0: ffff888011866538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:663 [inline]
#0: ffff888011866538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x87a/0x1610 kernel/workqueue.c:2260
#1: ffffc90014d07da8 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x8ae/0x1610 kernel/workqueue.c:2264
task:syz-executor.1 state:D stack:26208 pid:19798 ppid:3629 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
io_schedule+0xba/0x130 kernel/sched/core.c:8714
folio_wait_bit_common+0x3dd/0xa90 mm/filemap.c:1298
__folio_lock mm/filemap.c:1664 [inline]
folio_lock include/linux/pagemap.h:939 [inline]
folio_lock include/linux/pagemap.h:935 [inline]
__filemap_get_folio+0xc6d/0xed0 mm/filemap.c:1936
truncate_inode_pages_range+0x37c/0x1510 mm/truncate.c:378
ntfs_evict_inode+0x16/0xa0 fs/ntfs3/inode.c:1741
evict+0x2ed/0x6b0 fs/inode.c:665
iput_final fs/inode.c:1748 [inline]
iput.part.0+0x55d/0x810 fs/inode.c:1774
iput+0x58/0x70 fs/inode.c:1764
ntfs_fill_super+0x2e89/0x37f0 fs/ntfs3/super.c:1190
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f50d0c8a7aa
RSP: 002b:00007f50d1d0bf88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f50d0c8a7aa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f50d1d0bfe0
RBP: 00007f50d1d0c020 R08: 00007f50d1d0c020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f50d1d0bfe0 R15: 000000002007aa80
</TASK>
1 lock held by syz-executor.1/19798:
#0: ffff8880520700e0 (&type->s_umount_key#47/1){+.+.}-{3:3}, at: alloc_super+0x22e/0xb60 fs/super.c:228
task:syz-executor.4 state:D stack:29248 pid:21701 ppid:3630 flags:0x00000004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6629
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0xa44/0x1350 kernel/locking/mutex.c:747
exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
synchronize_rcu_expedited+0x24a/0x670 kernel/rcu/tree_exp.h:940
synchronize_rcu+0x2c3/0x370 kernel/rcu/tree.c:3519
__sched_core_enable kernel/sched/core.c:387 [inline]
sched_core_get+0x87/0xa0 kernel/sched/core.c:406
sched_core_alloc_cookie kernel/sched/core_sched.c:18 [inline]
sched_core_share_pid+0x3d7/0x9a0 kernel/sched/core_sched.c:185
__do_sys_prctl+0x7de/0x1380 kernel/sys.c:2620
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0781a89279
RSP: 002b:00007f0782c50168 EFLAGS: 00000246 ORIG_RAX: 000000000000009d
RAX: ffffffffffffffda RBX: 00007f0781b9bf80 RCX: 00007f0781a89279
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 000000000000003e
RBP: 00007f0781ae3189 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcf62129ef R14: 00007f0782c50300 R15: 0000000000022000
</TASK>
2 locks held by syz-executor.4/21701:
#0: ffffffff8be5e2c8 (sched_core_mutex){+.+.}-{3:3}, at: sched_core_get+0x37/0xa0 kernel/sched/core.c:404
#1: ffffffff8bf941b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
#1: ffffffff8bf941b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x24a/0x670 kernel/rcu/tree_exp.h:940
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 5.19.0-next-20220808-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
nmi_cpu_backtrace.cold+0x46/0x14f lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x206/0x250 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:227 [inline]
watchdog+0xcf7/0xfd0 kernel/hung_task.c:384
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 18028 Comm: kworker/0:1 Not tainted 5.19.0-next-20220808-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: events bpf_prog_free_deferred
RIP: 0010:stack_access_ok+0xe3/0x1d0 arch/x86/kernel/unwind_orc.c:347
Code: 03 80 3c 02 00 0f 85 e1 00 00 00 48 8b 73 28 48 89 da 48 89 ef e8 6d af f5 ff 85 c0 74 0f 31 c0 48 83 c4 08 5b 5d 41 5c 41 5d <41> 5e c3 48 8d 7b 08 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1
RSP: 0018:ffffc9000b827858 EFLAGS: 00000282
RAX: ffffc9000b828001 RBX: 0000000000000001 RCX: 0000000000000001
RDX: ffffc9000b827c01 RSI: ffffc9000b827ce8 RDI: ffffc9000b8278e8
RBP: ffffc9000b827920 R08: ffffffff8e6497f8 R09: ffffc9000b82790c
R10: fffff52001704f26 R11: ffffc9000b827d10 R12: ffffc9000b82790d
R13: ffffc9000b8278d8 R14: ffffc9000b827ce8 R15: ffffffff8e6497fc
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c004477000 CR3: 000000000bc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
deref_stack_reg arch/x86/kernel/unwind_orc.c:352 [inline]
unwind_next_frame+0x12b4/0x1cc0 arch/x86/kernel/unwind_orc.c:600
arch_stack_walk+0x7d/0xe0 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x8c/0xc0 kernel/stacktrace.c:122
save_stack+0x151/0x1e0 mm/page_owner.c:127
__reset_page_owner+0x59/0x170 mm/page_owner.c:148
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1449 [inline]
free_pcp_prepare+0x5e4/0xd20 mm/page_alloc.c:1499
free_unref_page_prepare mm/page_alloc.c:3380 [inline]
free_unref_page+0x19/0x4d0 mm/page_alloc.c:3476
__vunmap+0x85d/0xd30 mm/vmalloc.c:2696
__vfree+0x3c/0xd0 mm/vmalloc.c:2744
vfree+0x5a/0x90 mm/vmalloc.c:2775
bpf_prog_free_deferred+0x614/0x7f0 kernel/bpf/core.c:2562
process_one_work+0x991/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [syzbot] INFO: task hung in __filemap_get_folio
2022-08-08 8:05 [syzbot] INFO: task hung in __filemap_get_folio syzbot
@ 2022-09-10 7:06 ` syzbot
2022-09-23 18:45 ` syzbot
2023-10-03 20:11 ` [syzbot] [block] " syzbot
2 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2022-09-10 7:06 UTC (permalink / raw)
To: akpm, linux-fsdevel, linux-kernel, linux-mm, syzkaller-bugs, willy
syzbot has found a reproducer for the following issue on:
HEAD commit: e47eb90a0a9a Add linux-next specific files for 20220901
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12e05825080000
kernel config: https://syzkaller.appspot.com/x/.config?x=7933882276523081
dashboard link: https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116a3953080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0e9dc403e57033a74b1d@syzkaller.appspotmail.com
INFO: task syz-executor.3:5563 blocked for more than 143 seconds.
Not tainted 6.0.0-rc3-next-20220901-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D
stack:26944 pid:5563 ppid:3713 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5197 [inline]
__schedule+0xae5/0x52c0 kernel/sched/core.c:6509
schedule+0xda/0x1b0 kernel/sched/core.c:6585
io_schedule+0xba/0x130 kernel/sched/core.c:8729
folio_wait_bit_common+0x49f/0xa20 mm/filemap.c:1295
__folio_lock mm/filemap.c:1658 [inline]
folio_lock include/linux/pagemap.h:939 [inline]
folio_lock include/linux/pagemap.h:935 [inline]
__filemap_get_folio+0xc6d/0xed0 mm/filemap.c:1930
truncate_inode_pages_range+0x37c/0x1510 mm/truncate.c:378
ntfs_evict_inode+0x16/0xa0 fs/ntfs3/inode.c:1741
evict+0x2ed/0x6b0 fs/inode.c:666
iput_final fs/inode.c:1749 [inline]
iput.part.0+0x55d/0x810 fs/inode.c:1775
iput+0x58/0x70 fs/inode.c:1765
ntfs_fill_super+0x2309/0x37f0 fs/ntfs3/super.c:1278
get_tree_bdev+0x440/0x760 fs/super.c:1323
vfs_get_tree+0x89/0x2f0 fs/super.c:1530
do_new_mount fs/namespace.c:3040 [inline]
path_mount+0x1326/0x1e20 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__x64_sys_mount+0x27f/0x300 fs/namespace.c:3568
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f62c488a8fa
RSP: 002b:00007fff05d56558 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f62c488a8fa
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fff05d565b0
RBP: 00007fff05d565f0 R08: 00007fff05d565f0 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fff05d565b0 R15: 000000002007aa80
</TASK>
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.0.0-rc3-next-20220901-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
nmi_cpu_backtrace.cold+0x46/0x14f lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x206/0x250 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:227 [inline]
watchdog+0xcf7/0xfd0 kernel/hung_task.c:384
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 2973 Comm: udevd Not tainted 6.0.0-rc3-next-20220901-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
RIP: 0033:0x7f2aff58ebf8
Code: f8 c5 fa 7e 0f c5 fa 7e 16 c5 e9 74 d1 c5 f9 d7 c2 2d ff ff 00 00 0f 85 06 ff ff ff c3 0f 1f 44 00 00 c5 fa 6f 16 c5 e9 74 17 <c5> f9 d7 c2 2d ff ff 00 00 0f 85 e9 fe ff ff 48 8d 7c 17 f0 48 8d
RSP: 002b:00007fff5dda79e8 EFLAGS: 00000206
RAX: 0000000000000007 RBX: 000055e68d0e4a70 RCX: 0000000000000000
RDX: 000000000000001c RSI: 000055e68d0e44b4 RDI: 000055e68cdc2e44
RBP: 000055e68cdc3380 R08: 000000000000001c R09: 000000000000001c
R10: 0000000000000002 R11: 0000000000000020 R12: 0000000000003a94
R13: 0000000000000703 R14: 0000000000000000 R15: 0000000000000000
FS: 00007f2aff8ae840 GS: 0000000000000000
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [syzbot] INFO: task hung in __filemap_get_folio
2022-08-08 8:05 [syzbot] INFO: task hung in __filemap_get_folio syzbot
2022-09-10 7:06 ` syzbot
@ 2022-09-23 18:45 ` syzbot
2022-09-24 22:25 ` Matthew Wilcox
2023-10-03 20:11 ` [syzbot] [block] " syzbot
2 siblings, 1 reply; 5+ messages in thread
From: syzbot @ 2022-09-23 18:45 UTC (permalink / raw)
To: akpm, linux-fsdevel, linux-kernel, linux-mm, syzkaller-bugs, willy
syzbot has found a reproducer for the following issue on:
HEAD commit: bf682942cd26 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12096640880000
kernel config: https://syzkaller.appspot.com/x/.config?x=7db7ad17eb14cb7
dashboard link: https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116e80ff080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11bfbbcf080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0e9dc403e57033a74b1d@syzkaller.appspotmail.com
INFO: task udevd:3638 blocked for more than 143 seconds.
Not tainted 6.0.0-rc6-syzkaller-00210-gbf682942cd26 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd state:D stack:26248 pid: 3638 ppid: 2972 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
io_schedule+0xba/0x130 kernel/sched/core.c:8714
folio_wait_bit_common+0x3dd/0xa90 mm/filemap.c:1298
__folio_lock mm/filemap.c:1664 [inline]
folio_lock include/linux/pagemap.h:939 [inline]
folio_lock include/linux/pagemap.h:935 [inline]
__filemap_get_folio+0xc6d/0xed0 mm/filemap.c:1936
truncate_inode_pages_range+0x37c/0x1510 mm/truncate.c:378
kill_bdev block/bdev.c:75 [inline]
blkdev_flush_mapping+0x140/0x2f0 block/bdev.c:661
blkdev_put_whole+0xd1/0xf0 block/bdev.c:692
blkdev_put+0x226/0x770 block/bdev.c:952
blkdev_close+0x64/0x80 block/fops.c:499
__fput+0x277/0x9d0 fs/file_table.c:320
task_work_run+0xdd/0x1a0 kernel/task_work.c:177
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xad5/0x29b0 kernel/exit.c:795
do_group_exit+0xd2/0x2f0 kernel/exit.c:925
get_signal+0x238c/0x2610 kernel/signal.c:2857
arch_do_signal_or_restart+0x82/0x2300 arch/x86/kernel/signal.c:869
exit_to_user_mode_loop kernel/entry/common.c:166 [inline]
exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:201
__syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:294
do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fea11178697
RSP: 002b:00007ffc3c7fb710 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: 0000000000000008 RBX: 000055b3e78469c0 RCX: 00007fea11178697
RDX: 00000000000a0800 RSI: 000055b3e7818920 RDI: 00000000ffffff9c
RBP: 000055b3e7818920 R08: 0000000000000001 R09: 00007ffc3c816080
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000a0800
R13: 000055b3e7819a80 R14: 00007ffc3c7fb7bc R15: 000055b3e780b2c0
</TASK>
INFO: task syz-executor127:3645 blocked for more than 143 seconds.
Not tainted 6.0.0-rc6-syzkaller-00210-gbf682942cd26 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor127 state:D stack:28376 pid: 3645 ppid: 3635 flags:0x00000004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5182 [inline]
__schedule+0xadf/0x52b0 kernel/sched/core.c:6494
schedule+0xda/0x1b0 kernel/sched/core.c:6570
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6629
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0xa44/0x1350 kernel/locking/mutex.c:747
blkdev_get_by_dev.part.0+0x9b/0xb90 block/bdev.c:812
blkdev_get_by_dev+0x6b/0x80 block/bdev.c:855
blkdev_open+0x13c/0x2c0 block/fops.c:485
do_dentry_open+0x4a4/0x13a0 fs/open.c:880
do_open fs/namei.c:3557 [inline]
path_openat+0x1c92/0x28f0 fs/namei.c:3691
do_filp_open+0x1b6/0x400 fs/namei.c:3718
do_sys_openat2+0x16d/0x4c0 fs/open.c:1313
do_sys_open fs/open.c:1329 [inline]
__do_sys_openat fs/open.c:1345 [inline]
__se_sys_openat fs/open.c:1340 [inline]
__x64_sys_openat+0x13f/0x1f0 fs/open.c:1340
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff1e173a4d7
RSP: 002b:00007ffdf8c863c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff1e173a4d7
RDX: 0000000000000000 RSI: 00007ffdf8c86440 RDI: 00000000ffffff9c
RBP: 00007ffdf8c86440 R08: 000000000000ffff R09: 00007ffdf8c862d0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8bf85db0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8bf85ab0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
1 lock held by khungtaskd/28:
#0: ffffffff8bf86900 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6492
1 lock held by klogd/2961:
#0: ffff8880b9a3a018 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2b/0x120 kernel/sched/core.c:544
2 locks held by getty/3287:
#0: ffff88801caa6098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
#1: ffffc90001c482f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef0/0x13e0 drivers/tty/n_tty.c:2177
1 lock held by udevd/3638:
#0: ffff88801e6644c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xbc/0x770 block/bdev.c:910
1 lock held by syz-executor127/3645:
#0: ffff88801e6644c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev.part.0+0x9b/0xb90 block/bdev.c:812
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.0.0-rc6-syzkaller-00210-gbf682942cd26 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
nmi_cpu_backtrace.cold+0x46/0x14f lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x206/0x250 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+0xc18/0xf50 kernel/hung_task.c:369
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 41 Comm: kworker/u4:2 Not tainted 6.0.0-rc6-syzkaller-00210-gbf682942cd26 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4741 [inline]
RIP: 0010:__lock_acquire+0x574/0x56d0 kernel/locking/lockdep.c:5003
Code: 00 00 45 89 fe 41 83 ee 01 0f 88 7c 13 00 00 49 b9 00 00 00 00 00 fc ff df 49 63 c6 48 8d 04 80 49 8d ac c5 99 0a 00 00 eb 12 <41> 83 ee 01 48 83 ed 28 41 83 fe ff 0f 84 15 0b 00 00 48 8d 5d df
RSP: 0018:ffffc90000d2f738 EFLAGS: 00000046
RAX: 0000000000000000 RBX: ffff8880174d0af8 RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffffff908e8dd9
RBP: ffff8880174d0b19 R08: 0000000000000000 R09: dffffc0000000000
R10: fffffbfff211c32a R11: 0000000000000000 R12: ffff8880174d0bc0
R13: ffff8880174d0080 R14: 0000000000000000 R15: 0000000000000005
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056317ad90680 CR3: 000000000bc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire kernel/locking/lockdep.c:5666 [inline]
lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5631
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:349 [inline]
__get_locked_pte+0x154/0x270 mm/memory.c:1838
get_locked_pte include/linux/mm.h:2089 [inline]
__text_poke+0x1b3/0x8e0 arch/x86/kernel/alternative.c:1123
text_poke arch/x86/kernel/alternative.c:1208 [inline]
text_poke_bp_batch+0x147/0x6c0 arch/x86/kernel/alternative.c:1487
text_poke_flush arch/x86/kernel/alternative.c:1660 [inline]
text_poke_flush arch/x86/kernel/alternative.c:1657 [inline]
text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1667
arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
jump_label_update+0x32f/0x410 kernel/jump_label.c:801
static_key_disable_cpuslocked+0x152/0x1b0 kernel/jump_label.c:207
static_key_disable+0x16/0x20 kernel/jump_label.c:215
toggle_allocation_gate mm/kfence/core.c:825 [inline]
toggle_allocation_gate+0x183/0x390 mm/kfence/core.c:803
process_one_work+0x991/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.080 msecs
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [syzbot] INFO: task hung in __filemap_get_folio
2022-09-23 18:45 ` syzbot
@ 2022-09-24 22:25 ` Matthew Wilcox
0 siblings, 0 replies; 5+ messages in thread
From: Matthew Wilcox @ 2022-09-24 22:25 UTC (permalink / raw)
To: syzbot; +Cc: akpm, linux-fsdevel, linux-kernel, linux-mm, syzkaller-bugs
On Fri, Sep 23, 2022 at 11:45:46AM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
No, it hasn't. This is a different bug. The other one is a bug in
NTFS. This is ... something else? Maybe nbd? maybe fuse?
> HEAD commit: bf682942cd26 Merge tag 'scsi-fixes' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12096640880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=7db7ad17eb14cb7
> dashboard link: https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116e80ff080000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11bfbbcf080000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+0e9dc403e57033a74b1d@syzkaller.appspotmail.com
>
> INFO: task udevd:3638 blocked for more than 143 seconds.
> Not tainted 6.0.0-rc6-syzkaller-00210-gbf682942cd26 #0
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:udevd state:D stack:26248 pid: 3638 ppid: 2972 flags:0x00004006
> Call Trace:
> <TASK>
> context_switch kernel/sched/core.c:5182 [inline]
> __schedule+0xadf/0x52b0 kernel/sched/core.c:6494
> schedule+0xda/0x1b0 kernel/sched/core.c:6570
> io_schedule+0xba/0x130 kernel/sched/core.c:8714
> folio_wait_bit_common+0x3dd/0xa90 mm/filemap.c:1298
> __folio_lock mm/filemap.c:1664 [inline]
> folio_lock include/linux/pagemap.h:939 [inline]
> folio_lock include/linux/pagemap.h:935 [inline]
> __filemap_get_folio+0xc6d/0xed0 mm/filemap.c:1936
> truncate_inode_pages_range+0x37c/0x1510 mm/truncate.c:378
> kill_bdev block/bdev.c:75 [inline]
> blkdev_flush_mapping+0x140/0x2f0 block/bdev.c:661
> blkdev_put_whole+0xd1/0xf0 block/bdev.c:692
> blkdev_put+0x226/0x770 block/bdev.c:952
> blkdev_close+0x64/0x80 block/fops.c:499
> __fput+0x277/0x9d0 fs/file_table.c:320
> task_work_run+0xdd/0x1a0 kernel/task_work.c:177
> exit_task_work include/linux/task_work.h:38 [inline]
> do_exit+0xad5/0x29b0 kernel/exit.c:795
> do_group_exit+0xd2/0x2f0 kernel/exit.c:925
> get_signal+0x238c/0x2610 kernel/signal.c:2857
> arch_do_signal_or_restart+0x82/0x2300 arch/x86/kernel/signal.c:869
> exit_to_user_mode_loop kernel/entry/common.c:166 [inline]
> exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:201
> __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
> syscall_exit_to_user_mode+0x19/0x50 kernel/entry/common.c:294
> do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
> RIP: 0033:0x7fea11178697
> RSP: 002b:00007ffc3c7fb710 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
> RAX: 0000000000000008 RBX: 000055b3e78469c0 RCX: 00007fea11178697
> RDX: 00000000000a0800 RSI: 000055b3e7818920 RDI: 00000000ffffff9c
> RBP: 000055b3e7818920 R08: 0000000000000001 R09: 00007ffc3c816080
> R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000a0800
> R13: 000055b3e7819a80 R14: 00007ffc3c7fb7bc R15: 000055b3e780b2c0
> </TASK>
> INFO: task syz-executor127:3645 blocked for more than 143 seconds.
> Not tainted 6.0.0-rc6-syzkaller-00210-gbf682942cd26 #0
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:syz-executor127 state:D stack:28376 pid: 3645 ppid: 3635 flags:0x00000004
> Call Trace:
> <TASK>
> context_switch kernel/sched/core.c:5182 [inline]
> __schedule+0xadf/0x52b0 kernel/sched/core.c:6494
> schedule+0xda/0x1b0 kernel/sched/core.c:6570
> schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6629
> __mutex_lock_common kernel/locking/mutex.c:679 [inline]
> __mutex_lock+0xa44/0x1350 kernel/locking/mutex.c:747
> blkdev_get_by_dev.part.0+0x9b/0xb90 block/bdev.c:812
> blkdev_get_by_dev+0x6b/0x80 block/bdev.c:855
> blkdev_open+0x13c/0x2c0 block/fops.c:485
> do_dentry_open+0x4a4/0x13a0 fs/open.c:880
> do_open fs/namei.c:3557 [inline]
> path_openat+0x1c92/0x28f0 fs/namei.c:3691
> do_filp_open+0x1b6/0x400 fs/namei.c:3718
> do_sys_openat2+0x16d/0x4c0 fs/open.c:1313
> do_sys_open fs/open.c:1329 [inline]
> __do_sys_openat fs/open.c:1345 [inline]
> __se_sys_openat fs/open.c:1340 [inline]
> __x64_sys_openat+0x13f/0x1f0 fs/open.c:1340
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
> RIP: 0033:0x7ff1e173a4d7
> RSP: 002b:00007ffdf8c863c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ff1e173a4d7
> RDX: 0000000000000000 RSI: 00007ffdf8c86440 RDI: 00000000ffffff9c
> RBP: 00007ffdf8c86440 R08: 000000000000ffff R09: 00007ffdf8c862d0
> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
> R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
> </TASK>
>
> Showing all locks held in the system:
> 1 lock held by rcu_tasks_kthre/12:
> #0: ffffffff8bf85db0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
> 1 lock held by rcu_tasks_trace/13:
> #0: ffffffff8bf85ab0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xc70 kernel/rcu/tasks.h:507
> 1 lock held by khungtaskd/28:
> #0: ffffffff8bf86900 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x53/0x260 kernel/locking/lockdep.c:6492
> 1 lock held by klogd/2961:
> #0: ffff8880b9a3a018 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2b/0x120 kernel/sched/core.c:544
> 2 locks held by getty/3287:
> #0: ffff88801caa6098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:244
> #1: ffffc90001c482f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef0/0x13e0 drivers/tty/n_tty.c:2177
> 1 lock held by udevd/3638:
> #0: ffff88801e6644c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xbc/0x770 block/bdev.c:910
> 1 lock held by syz-executor127/3645:
> #0: ffff88801e6644c8 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev.part.0+0x9b/0xb90 block/bdev.c:812
>
> =============================================
>
> NMI backtrace for cpu 1
> CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.0.0-rc6-syzkaller-00210-gbf682942cd26 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
> Call Trace:
> <TASK>
> __dump_stack lib/dump_stack.c:88 [inline]
> dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
> nmi_cpu_backtrace.cold+0x46/0x14f lib/nmi_backtrace.c:111
> nmi_trigger_cpumask_backtrace+0x206/0x250 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+0xc18/0xf50 kernel/hung_task.c:369
> kthread+0x2e4/0x3a0 kernel/kthread.c:376
> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
> </TASK>
> Sending NMI from CPU 1 to CPUs 0:
> NMI backtrace for cpu 0
> CPU: 0 PID: 41 Comm: kworker/u4:2 Not tainted 6.0.0-rc6-syzkaller-00210-gbf682942cd26 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
> Workqueue: events_unbound toggle_allocation_gate
> RIP: 0010:check_wait_context kernel/locking/lockdep.c:4741 [inline]
> RIP: 0010:__lock_acquire+0x574/0x56d0 kernel/locking/lockdep.c:5003
> Code: 00 00 45 89 fe 41 83 ee 01 0f 88 7c 13 00 00 49 b9 00 00 00 00 00 fc ff df 49 63 c6 48 8d 04 80 49 8d ac c5 99 0a 00 00 eb 12 <41> 83 ee 01 48 83 ed 28 41 83 fe ff 0f 84 15 0b 00 00 48 8d 5d df
> RSP: 0018:ffffc90000d2f738 EFLAGS: 00000046
> RAX: 0000000000000000 RBX: ffff8880174d0af8 RCX: 0000000000000001
> RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffffff908e8dd9
> RBP: ffff8880174d0b19 R08: 0000000000000000 R09: dffffc0000000000
> R10: fffffbfff211c32a R11: 0000000000000000 R12: ffff8880174d0bc0
> R13: ffff8880174d0080 R14: 0000000000000000 R15: 0000000000000005
> FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000056317ad90680 CR3: 000000000bc8e000 CR4: 00000000003506f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> lock_acquire kernel/locking/lockdep.c:5666 [inline]
> lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5631
> __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
> _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
> spin_lock include/linux/spinlock.h:349 [inline]
> __get_locked_pte+0x154/0x270 mm/memory.c:1838
> get_locked_pte include/linux/mm.h:2089 [inline]
> __text_poke+0x1b3/0x8e0 arch/x86/kernel/alternative.c:1123
> text_poke arch/x86/kernel/alternative.c:1208 [inline]
> text_poke_bp_batch+0x147/0x6c0 arch/x86/kernel/alternative.c:1487
> text_poke_flush arch/x86/kernel/alternative.c:1660 [inline]
> text_poke_flush arch/x86/kernel/alternative.c:1657 [inline]
> text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1667
> arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
> jump_label_update+0x32f/0x410 kernel/jump_label.c:801
> static_key_disable_cpuslocked+0x152/0x1b0 kernel/jump_label.c:207
> static_key_disable+0x16/0x20 kernel/jump_label.c:215
> toggle_allocation_gate mm/kfence/core.c:825 [inline]
> toggle_allocation_gate+0x183/0x390 mm/kfence/core.c:803
> process_one_work+0x991/0x1610 kernel/workqueue.c:2289
> worker_thread+0x665/0x1080 kernel/workqueue.c:2436
> kthread+0x2e4/0x3a0 kernel/kthread.c:376
> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
> </TASK>
> INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.080 msecs
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [block] INFO: task hung in __filemap_get_folio
2022-08-08 8:05 [syzbot] INFO: task hung in __filemap_get_folio syzbot
2022-09-10 7:06 ` syzbot
2022-09-23 18:45 ` syzbot
@ 2023-10-03 20:11 ` syzbot
2 siblings, 0 replies; 5+ messages in thread
From: syzbot @ 2023-10-03 20:11 UTC (permalink / raw)
To: akpm, leon, linux-block, linux-fsdevel, linux-kernel, linux-mm,
sagi, saravanan.vajravel, selvin.xavier, syzkaller-bugs, willy
syzbot suspects this issue was fixed by commit:
commit 699826f4e30ab76a62c238c86fbef7e826639c8d
Author: Saravanan Vajravel <saravanan.vajravel@broadcom.com>
Date: Tue Jun 6 10:25:31 2023 +0000
IB/isert: Fix incorrect release of isert connection
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=144a99be680000
start commit: 105a36f3694e Merge tag 'kbuild-fixes-v6.0-3' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=122d7bd4fc8e0ecb
dashboard link: https://syzkaller.appspot.com/bug?extid=0e9dc403e57033a74b1d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10174404880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169f552f080000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: IB/isert: Fix incorrect release of isert connection
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-10-03 20:11 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-08 8:05 [syzbot] INFO: task hung in __filemap_get_folio syzbot
2022-09-10 7:06 ` syzbot
2022-09-23 18:45 ` syzbot
2022-09-24 22:25 ` Matthew Wilcox
2023-10-03 20:11 ` [syzbot] [block] " syzbot
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.