[v6.1] INFO: task hung in user_get_super

0 views
Skip to first unread message

syzbot

unread,
Apr 10, 2023, 3:19:45 AM4/10/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 543aff194ab6 Linux 6.1.23
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13087273c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9affea290775ea7
dashboard link: https://syzkaller.appspot.com/bug?extid=4aed00cd1e177d0d6a44
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6fe9097a8f09/disk-543aff19.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9df5aa0f6266/vmlinux-543aff19.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84127c4bde2b/bzImage-543aff19.xz

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

INFO: task syz-executor.4:13213 blocked for more than 143 seconds.
Not tainted 6.1.23-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:26312 pid:13213 ppid:22542 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6689
rwsem_down_read_slowpath+0x5f0/0x940 kernel/locking/rwsem.c:1094
__down_read_common+0x61/0x2c0 kernel/locking/rwsem.c:1261
user_get_super+0x11a/0x250 fs/super.c:878
quotactl_block fs/quota/quota.c:890 [inline]
__do_sys_quotactl fs/quota/quota.c:954 [inline]
__se_sys_quotactl+0x490/0x770 fs/quota/quota.c:916
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f200248c169
RSP: 002b:00007f2003199168 EFLAGS: 00000246 ORIG_RAX: 00000000000000b3
RAX: ffffffffffffffda RBX: 00007f20025abf80 RCX: 00007f200248c169
RDX: 0000000000000000 RSI: 0000000020000040 RDI: ffffffff80000402
RBP: 00007f20024e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd6221272f R14: 00007f2003199300 R15: 0000000000022000
</TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cf26830 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cf27030 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffffffff8cf26660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3316:
#0: ffff88814ae97098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2177
1 lock held by syz-executor.4/22414:
3 locks held by kworker/u4:11/2705:
1 lock held by syz-executor.4/13213:
#0: ffff8880791d60e0 (&type->s_umount_key#59){++++}-{3:3}, at: user_get_super+0x11a/0x250 fs/super.c:878
1 lock held by syz-executor.4/13296:
#0: ffff8880791d60e0 (&type->s_umount_key#59){++++}-{3:3}, at: user_get_super+0x11a/0x250 fs/super.c:878
1 lock held by syz-executor.2/13846:
2 locks held by syz-executor.5/13853:
3 locks held by syz-executor.5/13861:
2 locks held by syz-executor.3/13863:
3 locks held by syz-executor.5/13867:

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf18/0xf60 kernel/hung_task.c:377
kthread+0x268/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 13863 Comm: syz-executor.3 Not tainted 6.1.23-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:29 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
RIP: 0010:lock_release+0x604/0xa20 kernel/locking/lockdep.c:5692
Code: 01 0f 85 94 00 00 00 4c 89 f3 48 c1 eb 03 42 80 3c 3b 00 74 08 4c 89 f7 e8 69 e0 75 00 48 c7 84 24 90 00 00 00 00 00 00 00 9c <8f> 84 24 90 00 00 00 42 80 3c 3b 00 74 08 4c 89 f7 e8 c6 df 75 00
RSP: 0018:ffffc900154cefb8 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 1ffff92002a99e0a RCX: ffffc900154cf003
RDX: 0000000000000002 RSI: ffffffff8aebd760 RDI: ffffffff8b3cb7e0
RBP: ffffc900154cf0f0 R08: dffffc0000000000 R09: fffffbfff1ca4dee
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92002a99e04
R13: 0000000000000246 R14: ffffc900154cf050 R15: dffffc0000000000
FS: 00007fadce7f9700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe104e1e000 CR3: 00000000212f7000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
prep_new_page mm/page_alloc.c:2540 [inline]
get_page_from_freelist+0x32ed/0x3480 mm/page_alloc.c:4292
__alloc_pages+0x28d/0x770 mm/page_alloc.c:5559
__folio_alloc+0xf/0x30 mm/page_alloc.c:5591
vma_alloc_folio+0x486/0x990 mm/mempolicy.c:2248
shmem_alloc_folio mm/shmem.c:1570 [inline]
shmem_alloc_and_acct_folio+0x5a8/0xd50 mm/shmem.c:1594
shmem_get_folio_gfp+0x13f0/0x3470 mm/shmem.c:1922
shmem_get_folio mm/shmem.c:2053 [inline]
shmem_write_begin+0x16e/0x4e0 mm/shmem.c:2540
generic_perform_write+0x2fc/0x5e0 mm/filemap.c:3754
__generic_file_write_iter+0x176/0x400 mm/filemap.c:3882
generic_file_write_iter+0xab/0x310 mm/filemap.c:3914
call_write_iter include/linux/fs.h:2205 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x7ae/0xba0 fs/read_write.c:584
ksys_write+0x19c/0x2c0 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fadcda3deef
Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 99 fd ff ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 cc fd ff ff 48
RSP: 002b:00007fadce7f8f10 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fadcda3deef
RDX: 0000000001000000 RSI: 00007fadc41ff000 RDI: 0000000000000003
RBP: 00007fadc41ff000 R08: 0000000000000000 R09: 00000000000050e8
R10: 0000000001000000 R11: 0000000000000293 R12: 0000000000000000
R13: 00007fadce7f8fdc R14: 00007fadce7f8fe0 R15: 0000000020005142
</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.

syzbot

unread,
Aug 14, 2023, 11:00:44 PM8/14/23
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