INFO: task hung in do_read_cache_page

7 views
Skip to first unread message

syzbot

unread,
Jun 9, 2022, 9:27:23 PM6/9/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b8f3be299d51 Linux 4.14.282
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11dc935ff00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f19bc3398ea47b8
dashboard link: https://syzkaller.appspot.com/bug?extid=53a9ff1724ef212b490e
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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+53a9ff...@syzkaller.appspotmail.com

block nbd1: shutting down sockets
block nbd0: Device being setup by another task
block nbd0: Receive control failed (result -32)
block nbd0: shutting down sockets
block nbd3: shutting down sockets
INFO: task systemd-udevd:22979 blocked for more than 140 seconds.
Not tainted 4.14.282-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
systemd-udevd D27464 22979 4631 0x00000300
Call Trace:
context_switch kernel/sched/core.c:2811 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3387
schedule+0x8d/0x1b0 kernel/sched/core.c:3431
io_schedule+0xb5/0x120 kernel/sched/core.c:5035
wait_on_page_bit_common mm/filemap.c:1025 [inline]
wait_on_page_bit+0x241/0x320 mm/filemap.c:1058
wait_on_page_locked include/linux/pagemap.h:527 [inline]
wait_on_page_read mm/filemap.c:2680 [inline]
do_read_cache_page+0x55f/0xc10 mm/filemap.c:2719
read_mapping_page include/linux/pagemap.h:398 [inline]
read_dev_sector+0xbd/0x3c0 block/partition-generic.c:659
read_part_sector block/partitions/check.h:38 [inline]
adfspart_check_ICS+0xf6/0xc00 block/partitions/acorn.c:366
check_partition+0x330/0x610 block/partitions/check.c:167
rescan_partitions+0x192/0x800 block/partition-generic.c:523
__blkdev_get+0xd7f/0x1090 fs/block_dev.c:1541
blkdev_get+0x88/0x890 fs/block_dev.c:1611
blkdev_open+0x1cc/0x250 fs/block_dev.c:1772
do_dentry_open+0x44b/0xec0 fs/open.c:777
vfs_open+0x105/0x220 fs/open.c:888
do_last fs/namei.c:3428 [inline]
path_openat+0x628/0x2970 fs/namei.c:3569
do_filp_open+0x179/0x3c0 fs/namei.c:3603
do_sys_open+0x296/0x410 fs/open.c:1081
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f45dde95840
RSP: 002b:00007ffe8bd8d878 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0000561333c7c5c0 RCX: 00007f45dde95840
RDX: 0000561331cedfe3 RSI: 00000000000a0800 RDI: 0000561333c7b6f0
RBP: 00007ffe8bd8d9f0 R08: 0000561331ced670 R09: 0000000000000010
R10: 0000561331cedd0c R11: 0000000000000246 R12: 00007ffe8bd8d940
R13: 0000561333c7c3b0 R14: 0000000000000003 R15: 000000000000000e
INFO: task syz-executor.3:22992 blocked for more than 140 seconds.
Not tainted 4.14.282-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.3 D28912 22992 8007 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2811 [inline]
__schedule+0x88b/0x1de0 kernel/sched/core.c:3387
schedule+0x8d/0x1b0 kernel/sched/core.c:3431
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3489
__mutex_lock_common kernel/locking/mutex.c:833 [inline]
__mutex_lock+0x669/0x1310 kernel/locking/mutex.c:893
blkdev_put+0x27/0x4c0 fs/block_dev.c:1826
blkdev_close+0x86/0xb0 fs/block_dev.c:1875
__fput+0x25f/0x7a0 fs/file_table.c:210
task_work_run+0x11f/0x190 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:191 [inline]
exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fe0da6b3d4b
RSP: 002b:00007ffc5e9dfa70 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007fe0da6b3d4b
RDX: 0000001b2fe20000 RSI: 0000001b2fe21c5c RDI: 0000000000000004
RBP: 00007fe0da815960 R08: 0000000000000000 R09: 00000000748f6f19
R10: 000b88a0babb003b R11: 0000000000000293 R12: 0000000000138d6a
R13: 00007ffc5e9dfb70 R14: 00007ffc5e9dfb90 R15: 0000000000000032

Showing all locks held in the system:
1 lock held by khungtaskd/1526:
#0: (tasklist_lock){.+.+}, at: [<ffffffff87026d5c>] debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4548
1 lock held by systemd-udevd/22979:
#0: (&bdev->bd_mutex){+.+.}, at: [<ffffffff81941ee1>] __blkdev_get+0x191/0x1090 fs/block_dev.c:1455
1 lock held by syz-executor.3/22992:
#0: (&bdev->bd_mutex){+.+.}, at: [<ffffffff819409a7>] blkdev_put+0x27/0x4c0 fs/block_dev.c:1826

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 1526 Comm: khungtaskd Not tainted 4.14.282-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
nmi_cpu_backtrace.cold+0x57/0x93 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x13a/0x180 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:140 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:195 [inline]
watchdog+0x5b9/0xb40 kernel/hung_task.c:274
kthread+0x30d/0x420 kernel/kthread.c:232
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at pc 0xffffffff87246dce


---
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.

syzbot

unread,
Nov 13, 2022, 12:53:37 PM11/13/22
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages