INFO: task hung in path_openat
19 views
Skip to first unread message
syzbot
Aug 11, 2019, 5:00:06 AM8/11/19
to syzkaller...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 893af1c7 Linux 4.19.66
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17002202600000
kernel config: https://syzkaller.appspot.com/x/.config?x=d5fac5a8617b8643
dashboard link: https://syzkaller.appspot.com/bug?extid=47d57530f2c0cbbc8434
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+47d575...@syzkaller.appspotmail.com
team0 (unregistering): Port device team_slave_0 removed
bond0 (unregistering): Releasing backup interface bond_slave_1
bond0 (unregistering): Releasing backup interface bond_slave_0
bond0 (unregistering): Released all slaves
INFO: task syz-executor.1:19785 blocked for more than 140 seconds.
Not tainted 4.19.66 #40
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.1 D29304 19785 12903 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2826 [inline]
__schedule+0x866/0x1dc0 kernel/sched/core.c:3474
schedule+0x92/0x1c0 kernel/sched/core.c:3518
__rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:589 [inline]
rwsem_down_write_failed+0x774/0xc30 kernel/locking/rwsem-xadd.c:618
call_rwsem_down_write_failed+0x17/0x30 arch/x86/lib/rwsem.S:117
__down_write arch/x86/include/asm/rwsem.h:142 [inline]
down_write+0x53/0x90 kernel/locking/rwsem.c:72
inode_lock include/linux/fs.h:747 [inline]
do_last fs/namei.c:3321 [inline]
path_openat+0x1477/0x45e0 fs/namei.c:3534
do_filp_open+0x1a1/0x280 fs/namei.c:3564
do_sys_open+0x3fe/0x550 fs/open.c:1088
ksys_open include/linux/syscalls.h:1276 [inline]
__do_sys_creat fs/open.c:1146 [inline]
__se_sys_creat fs/open.c:1144 [inline]
__x64_sys_creat+0x61/0x80 fs/open.c:1144
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x459829
Code: ff ff c3 c5 f8 77 eb 60 80 3d bc 39 39 01 01 0f 85 7f fd ff ff 48 83
f8 0c 0f 83 74 fe ff ff 48 8d 75 10 66 f7 c6 f0 0f 0f 84 <66> fd ff ff f3
0f 6f 4d 00 48 8d 74 17 f1 49 c7 c1 10 00 00 00 49
RSP: 002b:00007f107b6afc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 0000000000459829
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200002c0
RBP: 000000000075c118 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f107b6b06d4
R13: 00000000004bfe84 R14: 00000000004d1d20 R15: 00000000ffffffff
Showing all locks held in the system:
1 lock held by khungtaskd/1039:
#0: 00000000ed5d2c31 (rcu_read_lock){....}, at:
debug_show_all_locks+0x5f/0x27e kernel/locking/lockdep.c:4435
1 lock held by rsyslogd/7705:
#0: 000000005663979c (&f->f_pos_lock){+.+.}, at: __fdget_pos+0xee/0x110
fs/file.c:767
2 locks held by getty/7827:
#0: 00000000346ea347 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 00000000d5b2352e (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7828:
#0: 000000001ea63135 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 0000000032e7a697 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7829:
#0: 00000000e591b02a (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 0000000013ab1bb9 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7830:
#0: 0000000051d1d3d7 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 00000000eeae6943 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7831:
#0: 00000000159154bf (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 0000000035220459 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7832:
#0: 00000000127f98ac (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 00000000a21a6277 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7833:
#0: 00000000bc31c4a9 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 000000004d8ed4ab (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by syz-executor.1/19742:
#0: 00000000900de5aa (sb_writers#24){.+.+}, at: sb_start_write
include/linux/fs.h:1578 [inline]
#0: 00000000900de5aa (sb_writers#24){.+.+}, at: mnt_want_write+0x3f/0xc0
fs/namespace.c:360
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at: inode_lock
include/linux/fs.h:747 [inline]
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at: do_last
fs/namei.c:3321 [inline]
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at:
path_openat+0x1477/0x45e0 fs/namei.c:3534
2 locks held by syz-executor.1/19785:
#0: 00000000900de5aa (sb_writers#24){.+.+}, at: sb_start_write
include/linux/fs.h:1578 [inline]
#0: 00000000900de5aa (sb_writers#24){.+.+}, at: mnt_want_write+0x3f/0xc0
fs/namespace.c:360
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at: inode_lock
include/linux/fs.h:747 [inline]
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at: do_last
fs/namei.c:3321 [inline]
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at:
path_openat+0x1477/0x45e0 fs/namei.c:3534
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1039 Comm: khungtaskd Not tainted 4.19.66 #40
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
nmi_cpu_backtrace.cold+0x63/0xa4 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1b0/0x1f8 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x9df/0xee0 kernel/hung_task.c:287
kthread+0x354/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0x10
arch/x86/include/asm/irqflags.h:60
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot found the following crash on:
HEAD commit: 893af1c7 Linux 4.19.66
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17002202600000
kernel config: https://syzkaller.appspot.com/x/.config?x=d5fac5a8617b8643
dashboard link: https://syzkaller.appspot.com/bug?extid=47d57530f2c0cbbc8434
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+47d575...@syzkaller.appspotmail.com
team0 (unregistering): Port device team_slave_0 removed
bond0 (unregistering): Releasing backup interface bond_slave_1
bond0 (unregistering): Releasing backup interface bond_slave_0
bond0 (unregistering): Released all slaves
INFO: task syz-executor.1:19785 blocked for more than 140 seconds.
Not tainted 4.19.66 #40
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.1 D29304 19785 12903 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2826 [inline]
__schedule+0x866/0x1dc0 kernel/sched/core.c:3474
schedule+0x92/0x1c0 kernel/sched/core.c:3518
__rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:589 [inline]
rwsem_down_write_failed+0x774/0xc30 kernel/locking/rwsem-xadd.c:618
call_rwsem_down_write_failed+0x17/0x30 arch/x86/lib/rwsem.S:117
__down_write arch/x86/include/asm/rwsem.h:142 [inline]
down_write+0x53/0x90 kernel/locking/rwsem.c:72
inode_lock include/linux/fs.h:747 [inline]
do_last fs/namei.c:3321 [inline]
path_openat+0x1477/0x45e0 fs/namei.c:3534
do_filp_open+0x1a1/0x280 fs/namei.c:3564
do_sys_open+0x3fe/0x550 fs/open.c:1088
ksys_open include/linux/syscalls.h:1276 [inline]
__do_sys_creat fs/open.c:1146 [inline]
__se_sys_creat fs/open.c:1144 [inline]
__x64_sys_creat+0x61/0x80 fs/open.c:1144
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x459829
Code: ff ff c3 c5 f8 77 eb 60 80 3d bc 39 39 01 01 0f 85 7f fd ff ff 48 83
f8 0c 0f 83 74 fe ff ff 48 8d 75 10 66 f7 c6 f0 0f 0f 84 <66> fd ff ff f3
0f 6f 4d 00 48 8d 74 17 f1 49 c7 c1 10 00 00 00 49
RSP: 002b:00007f107b6afc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 0000000000459829
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200002c0
RBP: 000000000075c118 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f107b6b06d4
R13: 00000000004bfe84 R14: 00000000004d1d20 R15: 00000000ffffffff
Showing all locks held in the system:
1 lock held by khungtaskd/1039:
#0: 00000000ed5d2c31 (rcu_read_lock){....}, at:
debug_show_all_locks+0x5f/0x27e kernel/locking/lockdep.c:4435
1 lock held by rsyslogd/7705:
#0: 000000005663979c (&f->f_pos_lock){+.+.}, at: __fdget_pos+0xee/0x110
fs/file.c:767
2 locks held by getty/7827:
#0: 00000000346ea347 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 00000000d5b2352e (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7828:
#0: 000000001ea63135 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 0000000032e7a697 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7829:
#0: 00000000e591b02a (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 0000000013ab1bb9 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7830:
#0: 0000000051d1d3d7 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 00000000eeae6943 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7831:
#0: 00000000159154bf (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 0000000035220459 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7832:
#0: 00000000127f98ac (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 00000000a21a6277 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by getty/7833:
#0: 00000000bc31c4a9 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:363
#1: 000000004d8ed4ab (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x232/0x1b30 drivers/tty/n_tty.c:2154
2 locks held by syz-executor.1/19742:
#0: 00000000900de5aa (sb_writers#24){.+.+}, at: sb_start_write
include/linux/fs.h:1578 [inline]
#0: 00000000900de5aa (sb_writers#24){.+.+}, at: mnt_want_write+0x3f/0xc0
fs/namespace.c:360
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at: inode_lock
include/linux/fs.h:747 [inline]
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at: do_last
fs/namei.c:3321 [inline]
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at:
path_openat+0x1477/0x45e0 fs/namei.c:3534
2 locks held by syz-executor.1/19785:
#0: 00000000900de5aa (sb_writers#24){.+.+}, at: sb_start_write
include/linux/fs.h:1578 [inline]
#0: 00000000900de5aa (sb_writers#24){.+.+}, at: mnt_want_write+0x3f/0xc0
fs/namespace.c:360
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at: inode_lock
include/linux/fs.h:747 [inline]
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at: do_last
fs/namei.c:3321 [inline]
#1: 0000000013b4a401 (&sb->s_type->i_mutex_key#27){+.+.}, at:
path_openat+0x1477/0x45e0 fs/namei.c:3534
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 1039 Comm: khungtaskd Not tainted 4.19.66 #40
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x172/0x1f0 lib/dump_stack.c:113
nmi_cpu_backtrace.cold+0x63/0xa4 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1b0/0x1f8 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x9df/0xee0 kernel/hung_task.c:287
kthread+0x354/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0xe/0x10
arch/x86/include/asm/irqflags.h:60
---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot
Jan 11, 2020, 2:40:06 AM1/11/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Palash Oswal
Mar 2, 2021, 4:15:20 AM3/2/21
to syzkaller-lts-bugs
I'm curious why this bug was on the lts list and not on the bugs list?
Reply all
Reply to author
Forward
0 new messages