INFO: task hung in fsnotify_mark_destroy_list (2)

7 views
Skip to first unread message

syzbot

unread,
Jul 2, 2019, 12:40:06 PM7/2/19
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: ab758e10 Merge 4.9.184 into android-4.9
git tree: android-4.9
console output: https://syzkaller.appspot.com/x/log.txt?x=1730eecda00000
kernel config: https://syzkaller.appspot.com/x/.config?x=c2aad653d98c6f23
dashboard link: https://syzkaller.appspot.com/bug?extid=3e100387bce1e0e8b047
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+3e1003...@syzkaller.appspotmail.com

binder: BINDER_SET_CONTEXT_MGR already set
binder: 19860:19873 ioctl 40046207 0 returned -16
binder_alloc: 29494: binder_alloc_buf, no vma
binder: 19860:19873 transaction failed 29189/-3, size
-1939563849970379251--3120025010557080190 line 3265
INFO: task kworker/u4:3:5648 blocked for more than 140 seconds.
Not tainted 4.9.184+ #5
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/u4:3 D26176 5648 2 0x80000000
Workqueue: events_unbound fsnotify_mark_destroy_workfn
0000000000000087 ffff8800b14daf80 ffff8801d034b700 ffff8801db721000
ffff8801d6d98000 ffff8801db721018 ffff880092c9f730 ffffffff8280a5ce
0000000000000000 00000000000003b8 0000000000000002 ffff8801db7218f0
Call Trace:
[<00000000addb70bc>] schedule+0x92/0x1c0 kernel/sched/core.c:3546
[<00000000303b0a60>] schedule_timeout+0x766/0xe50 kernel/time/timer.c:1771
[<00000000d31ed4f8>] do_wait_for_common kernel/sched/completion.c:75
[inline]
[<00000000d31ed4f8>] __wait_for_common kernel/sched/completion.c:93
[inline]
[<00000000d31ed4f8>] wait_for_common+0x2c6/0x4d0
kernel/sched/completion.c:101
[<00000000cfbbde0b>] wait_for_completion+0x18/0x20
kernel/sched/completion.c:122
[<0000000055db402d>] __synchronize_srcu+0x26d/0x3d0 kernel/rcu/srcu.c:448
[<00000000d7cbed30>] synchronize_srcu+0x1f/0x40 kernel/rcu/srcu.c:492
[<000000001f536a2a>] fsnotify_mark_destroy_list+0x110/0x390
fs/notify/mark.c:551
[<000000004374caa1>] fsnotify_mark_destroy_workfn+0xe/0x10
fs/notify/mark.c:561
[<00000000b328c894>] process_one_work+0x88b/0x1600 kernel/workqueue.c:2114
[<000000009e806290>] worker_thread+0x5df/0x11d0 kernel/workqueue.c:2251
[<000000004988cc04>] kthread+0x278/0x310 kernel/kthread.c:211
[<00000000b39c7f10>] ret_from_fork+0x5c/0x70 arch/x86/entry/entry_64.S:375

Showing all locks held in the system:
2 locks held by khungtaskd/24:
#0: (rcu_read_lock){......}, at: [<0000000038082cfa>]
check_hung_uninterruptible_tasks kernel/hung_task.c:169 [inline]
#0: (rcu_read_lock){......}, at: [<0000000038082cfa>]
watchdog+0x14b/0xaf0 kernel/hung_task.c:263
#1: (tasklist_lock){.+.+..}, at: [<0000000056cb2df1>]
debug_show_all_locks+0x7f/0x21f kernel/locking/lockdep.c:4336
2 locks held by udevd/587:
#0: (&mm->mmap_sem){++++++}, at: [<00000000ce89f207>]
vm_mmap_pgoff+0x13d/0x1c0 mm/util.c:327
#1: (&anon_vma->rwsem){++++..}, at: [<00000000b4ce63b0>]
anon_vma_lock_read include/linux/rmap.h:127 [inline]
#1: (&anon_vma->rwsem){++++..}, at: [<00000000b4ce63b0>]
validate_mm+0xdb/0x5a0 mm/mmap.c:361
1 lock held by rsyslogd/1907:
#0: (&f->f_pos_lock){+.+.+.}, at: [<00000000664327ec>]
__fdget_pos+0xa8/0xd0 fs/file.c:782
2 locks held by getty/2035:
#0: (&tty->ldisc_sem){++++++}, at: [<00000000f4ba5115>]
ldsem_down_read+0x33/0x40 drivers/tty/tty_ldsem.c:377
#1: (&ldata->atomic_read_lock){+.+...}, at: [<00000000506ab620>]
n_tty_read+0x1fe/0x1820 drivers/tty/n_tty.c:2156
2 locks held by kworker/u4:3/5648:
#0: ("events_unbound"){.+.+.+}, at: [<00000000ca258bd3>]
process_one_work+0x790/0x1600 kernel/workqueue.c:2107
#1: ((reaper_work).work){+.+...}, at: [<00000000d973faa5>]
process_one_work+0x7ce/0x1600 kernel/workqueue.c:2111
1 lock held by init/11532:
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open_by_driver
drivers/tty/tty_io.c:2062 [inline]
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open+0x3f9/0xe10
drivers/tty/tty_io.c:2140
1 lock held by init/11533:
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open_by_driver
drivers/tty/tty_io.c:2062 [inline]
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open+0x3f9/0xe10
drivers/tty/tty_io.c:2140
1 lock held by init/11534:
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open_by_driver
drivers/tty/tty_io.c:2062 [inline]
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open+0x3f9/0xe10
drivers/tty/tty_io.c:2140
1 lock held by init/11535:
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open_by_driver
drivers/tty/tty_io.c:2062 [inline]
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open+0x3f9/0xe10
drivers/tty/tty_io.c:2140
1 lock held by init/11536:
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open_by_driver
drivers/tty/tty_io.c:2062 [inline]
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open+0x3f9/0xe10
drivers/tty/tty_io.c:2140
1 lock held by init/12018:
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open_by_driver
drivers/tty/tty_io.c:2062 [inline]
#0: (tty_mutex){+.+.+.}, at: [<00000000d04669af>] tty_open+0x3f9/0xe10
drivers/tty/tty_io.c:2140
2 locks held by syz-executor.3/19833:
#0: (&evdev->mutex){+.+...}, at: [<00000000053c7db8>] evdev_close_device
drivers/input/evdev.c:441 [inline]
#0: (&evdev->mutex){+.+...}, at: [<00000000053c7db8>]
evdev_release+0xf0/0x1b0 drivers/input/evdev.c:482
#1: (&dev->mutex#2){+.+...}, at: [<000000008640dd3b>]
input_close_device+0x48/0x140 drivers/input/input.c:650

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

NMI backtrace for cpu 0
CPU: 0 PID: 24 Comm: khungtaskd Not tainted 4.9.184+ #5
ffff8801d98efcc8 ffffffff81b580a1 0000000000000000 0000000000000000
0000000000000000 ffffffff81099a01 dffffc0000000000 ffff8801d98efd00
ffffffff81b6333c 0000000000000000 0000000000000000 0000000000000000
Call Trace:
[<000000009c78d1c9>] __dump_stack lib/dump_stack.c:15 [inline]
[<000000009c78d1c9>] dump_stack+0xc1/0x120 lib/dump_stack.c:51
[<000000007ee3f4be>] nmi_cpu_backtrace.cold+0x47/0x87
lib/nmi_backtrace.c:99
[<00000000ca24873b>] nmi_trigger_cpumask_backtrace+0x124/0x155
lib/nmi_backtrace.c:60
[<000000005c763935>] arch_trigger_cpumask_backtrace+0x14/0x20
arch/x86/kernel/apic/hw_nmi.c:37
[<0000000037427d62>] trigger_all_cpu_backtrace include/linux/nmi.h:58
[inline]
[<0000000037427d62>] check_hung_task kernel/hung_task.c:126 [inline]
[<0000000037427d62>] check_hung_uninterruptible_tasks
kernel/hung_task.c:183 [inline]
[<0000000037427d62>] watchdog+0x670/0xaf0 kernel/hung_task.c:263
[<000000004988cc04>] kthread+0x278/0x310 kernel/kthread.c:211
[<00000000b39c7f10>] ret_from_fork+0x5c/0x70 arch/x86/entry/entry_64.S:375
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 2351 Comm: kworker/1:2 Not tainted 4.9.184+ #5
Workqueue: events binder_deferred_func c
task: 00000000798c08bc task.stack: 0000000086ffd91f
RIP: 0010:[<ffffffff81d77c2b>] c [<00000000b24b3ef9>]
io_serial_in+0x6b/0x90 drivers/tty/serial/8250/8250_port.c:414
RSP: 0018:ffff8801a58b7648 EFLAGS: 00000002
RAX: dffffc0000000000 RBX: 00000000000003fd RCX: 0000000000000000
RDX: 00000000000003fd RSI: ffffffff81d77bd1 RDI: ffffffff84b65d18
RBP: ffff8801a58b7658 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: ffffffff841d4578 R12: ffffffff84b65ce0
R13: 0000000000000020 R14: fffffbfff096cbe3 R15: fffffbfff096cba5
FS: 0000000000000000(0000) GS:ffff8801db700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffd3648e0b8 CR3: 00000001d011a000 CR4: 00000000001606b0
Stack:
ffffffff84b65ce0 c 0000000000002707 c ffff8801a58b76a8 c ffffffff81d79e74 c
ffffffff841d4540 c ffffffff84b65d28 c ffffffff84b65f1a c ffffffff841d4568 c
ffffffff84b65ce0 c 0000000000000058 c dffffc0000000000 c 0000000000000058 c
Call Trace:
[<00000000a3f4a200>] serial_in drivers/tty/serial/8250/8250.h:111 [inline]
[<00000000a3f4a200>] wait_for_xmitr+0x94/0x1e0
drivers/tty/serial/8250/8250_port.c:1997
[<0000000056485c15>] serial8250_console_putchar+0x20/0x60
drivers/tty/serial/8250/8250_port.c:3103
[<0000000066b5e0ff>] uart_console_write+0x56/0xe0
drivers/tty/serial/serial_core.c:1880
[<00000000f6839469>] serial8250_console_write+0x2fb/0x860
drivers/tty/serial/8250/8250_port.c:3169
[<00000000757100ae>] univ8250_console_write+0x5f/0x70
drivers/tty/serial/8250/8250_core.c:594
[<000000007e6c8f4a>] call_console_drivers.isra.0.constprop.0+0x1ac/0x360
kernel/printk/printk.c:1594
[<00000000522e0281>] console_unlock+0x47c/0xb20 kernel/printk/printk.c:2454
[<000000007a4e826a>] vprintk_emit+0x43f/0x6f0 kernel/printk/printk.c:1908
[<000000005cb8c85b>] vprintk+0x28/0x30 kernel/printk/printk.c:1918
[<00000000dc96fb4b>] vprintk_func kernel/printk/internal.h:36 [inline]
[<00000000dc96fb4b>] printk+0xc2/0xf5 kernel/printk/printk.c:1980
[<00000000620bd59c>] binder_release_work.cold+0x78/0x9d
drivers/android/binder.c:4586
[<0000000006b2b5d8>] binder_thread_release+0x42e/0x530
drivers/android/binder.c:4777
[<00000000783eb9e9>] binder_deferred_release drivers/android/binder.c:5396
[inline]
[<00000000783eb9e9>] binder_deferred_func+0x499/0xde0
drivers/android/binder.c:5479
[<00000000b328c894>] process_one_work+0x88b/0x1600 kernel/workqueue.c:2114
[<000000009e806290>] worker_thread+0x5df/0x11d0 kernel/workqueue.c:2251
[<000000004988cc04>] kthread+0x278/0x310 kernel/kthread.c:211
[<00000000b39c7f10>] ret_from_fork+0x5c/0x70 arch/x86/entry/entry_64.S:375
Code: c24 cc9 c00 c00 c00 c49 c8d c7c c24 c38 c48 cb8 c00 c00
c00 c00 c00 cfc cff cdf c48 c89 cfa c48 cc1 cea c03 cd3 ce3
c80 c3c c02 c00 c75 c17 c41 c03 c5c c24 c38 c89 cda cec
c<5b> c0f cb6 cc0 c41 c5c c5d cc3 ce8 c38 c53 c78 cff ceb
cc2 ce8 c91 c53 c78 cff ceb c


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

unread,
Oct 25, 2019, 10:12:08 AM10/25/19
to syzkaller-a...@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