INFO: task hung in mon_bin_fetch
14 views
Skip to first unread message
syzbot
Sep 4, 2018, 11:41:05 PM9/4/18
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following crash on:
HEAD commit: 60c1f89241d4 Merge tag 'dma-mapping-4.19-2' of git://git.i..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13db6e3e400000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c7e83258d6e0156
dashboard link: https://syzkaller.appspot.com/bug?extid=38b514b9d1d6842f3da1
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [ar...@arndb.de gre...@linuxfoundation.org
jrdr....@gmail.com kees...@chromium.org kste...@linuxfoundation.org
linux-...@vger.kernel.org linu...@vger.kernel.org pombr...@nexb.com
tg...@linutronix.de vi...@zeniv.linux.org.uk zai...@redhat.com]
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+38b514...@syzkaller.appspotmail.com
INFO: task syz-executor7:2687 blocked for more than 140 seconds.
Not tainted 4.19.0-rc2+ #220
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor7 D24064 2687 4671 0x00000000
Call Trace:
context_switch kernel/sched/core.c:2825 [inline]
__schedule+0x87c/0x1df0 kernel/sched/core.c:3473
schedule+0xfb/0x450 kernel/sched/core.c:3517
schedule_preempt_disabled+0x10/0x20 kernel/sched/core.c:3575
__mutex_lock_common kernel/locking/mutex.c:1003 [inline]
__mutex_lock+0xbf9/0x1700 kernel/locking/mutex.c:1073
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1088
mon_bin_fetch+0x37/0x340 drivers/usb/mon/mon_bin.c:909
mon_bin_ioctl+0x2ab/0xe80 drivers/usb/mon/mon_bin.c:1091
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
audit: type=1326 audit(1536028223.489:208): auid=4294967295 uid=0 gid=0
ses=4294967295 subj==unconfined pid=25668 comm="syz-executor7"
exe="/root/syz-executor7" sig=9 arch=c000003e syscall=202 compat=0
ip=0x457099 code=0x0
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457099
Code: Bad RIP value.
RSP: 002b:00007ff17af19c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff17af1a6d4 RCX: 0000000000457099
RDX: 0000000020000000 RSI: 00000000c0109207 RDI: 0000000000000004
RBP: 00000000009301e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004cf640 R14: 00000000004c593b R15: 0000000000000002
Showing all locks held in the system:
1 lock held by khungtaskd/791:
#0: 00000000d1ef6de3 (rcu_read_lock){....}, at:
debug_show_all_locks+0xd0/0x428 kernel/locking/lockdep.c:4436
1 lock held by rsyslogd/4529:
2 locks held by getty/4619:
#0: 00000000396931ff (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 0000000008d53519 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4620:
#0: 000000006ea9f27f (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000558c0542 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4621:
#0: 00000000512c6393 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000005390b2b1 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4622:
#0: 00000000ffdec0b9 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000f32448cc (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4623:
#0: 00000000900e86a6 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 0000000072356feb (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4624:
#0: 000000007ece330f (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000b985a3d7 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4625:
#0: 00000000c41bf000 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000c832b76f (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
1 lock held by syz-executor7/2614:
#0: 0000000036f7c216 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x650
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor7/2687:
#0: 0000000036f7c216 (&rp->fetch_lock){+.+.}, at: mon_bin_fetch+0x37/0x340
drivers/usb/mon/mon_bin.c:909
1 lock held by syz-executor4/4574:
#0: 000000000f5aae49 (&sig->cred_guard_mutex){+.+.}, at:
prepare_bprm_creds+0x53/0x120 fs/exec.c:1404
1 lock held by syz-executor4/4592:
#0: 0000000041ca01b9 (&sig->cred_guard_mutex){+.+.}, at:
prepare_bprm_creds+0x53/0x120 fs/exec.c:1404
2 locks held by syz-executor7/25678:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 791 Comm: khungtaskd Not tainted 4.19.0-rc2+ #220
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+0x1c9/0x2b4 lib/dump_stack.c:113
nmi_cpu_backtrace.cold.3+0x48/0x88 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x151/0x192 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:144 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
watchdog+0xb39/0x1040 kernel/hung_task.c:265
kthread+0x35a/0x420 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:413
Sending NMI from CPU 0 to CPUs 1:
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.317
msecs
NMI backtrace for cpu 1
CPU: 1 PID: 25699 Comm: syz-executor6 Not tainted 4.19.0-rc2+ #220
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__preempt_count_sub arch/x86/include/asm/preempt.h:81 [inline]
RIP: 0010:rcu_read_unlock_sched_notrace include/linux/rcupdate.h:773
[inline]
RIP: 0010:trace_block_touch_buffer include/trace/events/block.h:45 [inline]
RIP: 0010:touch_buffer fs/buffer.c:58 [inline]
RIP: 0010:__find_get_block+0x7d5/0xdf0 fs/buffer.c:1298
Code: 1d e8 3f 12 a6 ff 0f b6 1d 2a 31 d4 06 31 ff 89 de e8 ff 12 a6 ff 84
db 0f 84 5e 03 00 00 e8 22 12 a6 ff 65 ff 0d cb 30 2b 7e <e9> 61 fb ff ff
4c 8b a5 78 fe ff ff 4c 8b bd 70 fe ff ff e8 03 12
RSP: 0000:ffff88008623ecb8 EFLAGS: 00000287
RAX: ffff880096afa100 RBX: 0000000000000001 RCX: ffffffff81d6c06c
RDX: 0000000000000000 RSI: ffffffff81d6bcfe RDI: 0000000000000005
RBP: ffff88008623ee48 R08: ffff880096afa100 R09: ffffed003b6246de
R10: ffffed003b6246de R11: ffff8801db1236f3 R12: 0000000000000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8801d56d00a8
FS: 00000000023d6940(0000) GS:ffff8801db100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2ca20000 CR3: 00000001050cb000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__getblk_gfp+0xde/0xb10 fs/buffer.c:1316
sb_getblk include/linux/buffer_head.h:325 [inline]
__ext4_get_inode_loc+0x408/0x1350 fs/ext4/inode.c:4564
ext4_get_inode_loc fs/ext4/inode.c:4677 [inline]
ext4_reserve_inode_write+0xf8/0x260 fs/ext4/inode.c:5834
ext4_mark_inode_dirty+0x182/0xab0 fs/ext4/inode.c:5986
ext4_dirty_inode+0x97/0xc0 fs/ext4/inode.c:6025
__mark_inode_dirty+0x760/0x1300 fs/fs-writeback.c:2129
generic_update_time+0x26a/0x450 fs/inode.c:1651
update_time fs/inode.c:1667 [inline]
file_update_time+0x390/0x640 fs/inode.c:1877
ext4_page_mkwrite+0x1fe/0x1430 fs/ext4/inode.c:6169
do_page_mkwrite+0x14e/0x520 mm/memory.c:2388
do_shared_fault mm/memory.c:3717 [inline]
do_fault mm/memory.c:3756 [inline]
handle_pte_fault mm/memory.c:3983 [inline]
__handle_mm_fault+0x2a0a/0x4350 mm/memory.c:4107
handle_mm_fault+0x53e/0xc80 mm/memory.c:4144
__do_page_fault+0x620/0xe50 arch/x86/mm/fault.c:1395
do_page_fault+0xf6/0x7a4 arch/x86/mm/fault.c:1470
page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1161
RIP: 0033:0x405947
Code: 00 00 00 48 83 ec 08 48 8b 15 15 a7 52 00 48 8b 05 06 a7 52 00 48 39
d0 48 8d 8a 00 00 00 01 72 17 48 39 c8 73 12 48 8d 50 04 <89> 38 48 89 15
e8 a6 52 00 48 83 c4 08 c3 48 89 c6 bf 58 bf 4b 00
RSP: 002b:0000000000a3fc10 EFLAGS: 00010287
RAX: 0000001b2ca20000 RBX: 0000000000000003 RCX: 0000001b2da20000
RDX: 0000001b2ca20004 RSI: 0000000000a3f9d0 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000013
R10: 0000000000000075 R11: 0000000000000246 R12: 0000000000000005
R13: 00000000000d23f0 R14: 00000000000000b7 R15: badc0ffeebadface
---
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#bug-status-tracking for how to communicate with
syzbot.
syzbot found the following crash on:
HEAD commit: 60c1f89241d4 Merge tag 'dma-mapping-4.19-2' of git://git.i..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13db6e3e400000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c7e83258d6e0156
dashboard link: https://syzkaller.appspot.com/bug?extid=38b514b9d1d6842f3da1
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
CC: [ar...@arndb.de gre...@linuxfoundation.org
jrdr....@gmail.com kees...@chromium.org kste...@linuxfoundation.org
linux-...@vger.kernel.org linu...@vger.kernel.org pombr...@nexb.com
tg...@linutronix.de vi...@zeniv.linux.org.uk zai...@redhat.com]
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+38b514...@syzkaller.appspotmail.com
INFO: task syz-executor7:2687 blocked for more than 140 seconds.
Not tainted 4.19.0-rc2+ #220
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor7 D24064 2687 4671 0x00000000
Call Trace:
context_switch kernel/sched/core.c:2825 [inline]
__schedule+0x87c/0x1df0 kernel/sched/core.c:3473
schedule+0xfb/0x450 kernel/sched/core.c:3517
schedule_preempt_disabled+0x10/0x20 kernel/sched/core.c:3575
__mutex_lock_common kernel/locking/mutex.c:1003 [inline]
__mutex_lock+0xbf9/0x1700 kernel/locking/mutex.c:1073
mutex_lock_nested+0x16/0x20 kernel/locking/mutex.c:1088
mon_bin_fetch+0x37/0x340 drivers/usb/mon/mon_bin.c:909
mon_bin_ioctl+0x2ab/0xe80 drivers/usb/mon/mon_bin.c:1091
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0x1de/0x1720 fs/ioctl.c:685
ksys_ioctl+0xa9/0xd0 fs/ioctl.c:702
__do_sys_ioctl fs/ioctl.c:709 [inline]
__se_sys_ioctl fs/ioctl.c:707 [inline]
__x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:707
do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
audit: type=1326 audit(1536028223.489:208): auid=4294967295 uid=0 gid=0
ses=4294967295 subj==unconfined pid=25668 comm="syz-executor7"
exe="/root/syz-executor7" sig=9 arch=c000003e syscall=202 compat=0
ip=0x457099 code=0x0
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457099
Code: Bad RIP value.
RSP: 002b:00007ff17af19c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff17af1a6d4 RCX: 0000000000457099
RDX: 0000000020000000 RSI: 00000000c0109207 RDI: 0000000000000004
RBP: 00000000009301e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 00000000004cf640 R14: 00000000004c593b R15: 0000000000000002
Showing all locks held in the system:
1 lock held by khungtaskd/791:
#0: 00000000d1ef6de3 (rcu_read_lock){....}, at:
debug_show_all_locks+0xd0/0x428 kernel/locking/lockdep.c:4436
1 lock held by rsyslogd/4529:
2 locks held by getty/4619:
#0: 00000000396931ff (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 0000000008d53519 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4620:
#0: 000000006ea9f27f (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000558c0542 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4621:
#0: 00000000512c6393 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 000000005390b2b1 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4622:
#0: 00000000ffdec0b9 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000f32448cc (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4623:
#0: 00000000900e86a6 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 0000000072356feb (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4624:
#0: 000000007ece330f (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000b985a3d7 (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/4625:
#0: 00000000c41bf000 (&tty->ldisc_sem){++++}, at:
ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:353
#1: 00000000c832b76f (&ldata->atomic_read_lock){+.+.}, at:
n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
1 lock held by syz-executor7/2614:
#0: 0000000036f7c216 (&rp->fetch_lock){+.+.}, at: mon_bin_read+0x60/0x650
drivers/usb/mon/mon_bin.c:813
1 lock held by syz-executor7/2687:
#0: 0000000036f7c216 (&rp->fetch_lock){+.+.}, at: mon_bin_fetch+0x37/0x340
drivers/usb/mon/mon_bin.c:909
1 lock held by syz-executor4/4574:
#0: 000000000f5aae49 (&sig->cred_guard_mutex){+.+.}, at:
prepare_bprm_creds+0x53/0x120 fs/exec.c:1404
1 lock held by syz-executor4/4592:
#0: 0000000041ca01b9 (&sig->cred_guard_mutex){+.+.}, at:
prepare_bprm_creds+0x53/0x120 fs/exec.c:1404
2 locks held by syz-executor7/25678:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 791 Comm: khungtaskd Not tainted 4.19.0-rc2+ #220
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+0x1c9/0x2b4 lib/dump_stack.c:113
nmi_cpu_backtrace.cold.3+0x48/0x88 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x151/0x192 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:144 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
watchdog+0xb39/0x1040 kernel/hung_task.c:265
kthread+0x35a/0x420 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:413
Sending NMI from CPU 0 to CPUs 1:
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.317
msecs
NMI backtrace for cpu 1
CPU: 1 PID: 25699 Comm: syz-executor6 Not tainted 4.19.0-rc2+ #220
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:__preempt_count_sub arch/x86/include/asm/preempt.h:81 [inline]
RIP: 0010:rcu_read_unlock_sched_notrace include/linux/rcupdate.h:773
[inline]
RIP: 0010:trace_block_touch_buffer include/trace/events/block.h:45 [inline]
RIP: 0010:touch_buffer fs/buffer.c:58 [inline]
RIP: 0010:__find_get_block+0x7d5/0xdf0 fs/buffer.c:1298
Code: 1d e8 3f 12 a6 ff 0f b6 1d 2a 31 d4 06 31 ff 89 de e8 ff 12 a6 ff 84
db 0f 84 5e 03 00 00 e8 22 12 a6 ff 65 ff 0d cb 30 2b 7e <e9> 61 fb ff ff
4c 8b a5 78 fe ff ff 4c 8b bd 70 fe ff ff e8 03 12
RSP: 0000:ffff88008623ecb8 EFLAGS: 00000287
RAX: ffff880096afa100 RBX: 0000000000000001 RCX: ffffffff81d6c06c
RDX: 0000000000000000 RSI: ffffffff81d6bcfe RDI: 0000000000000005
RBP: ffff88008623ee48 R08: ffff880096afa100 R09: ffffed003b6246de
R10: ffffed003b6246de R11: ffff8801db1236f3 R12: 0000000000000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8801d56d00a8
FS: 00000000023d6940(0000) GS:ffff8801db100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2ca20000 CR3: 00000001050cb000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__getblk_gfp+0xde/0xb10 fs/buffer.c:1316
sb_getblk include/linux/buffer_head.h:325 [inline]
__ext4_get_inode_loc+0x408/0x1350 fs/ext4/inode.c:4564
ext4_get_inode_loc fs/ext4/inode.c:4677 [inline]
ext4_reserve_inode_write+0xf8/0x260 fs/ext4/inode.c:5834
ext4_mark_inode_dirty+0x182/0xab0 fs/ext4/inode.c:5986
ext4_dirty_inode+0x97/0xc0 fs/ext4/inode.c:6025
__mark_inode_dirty+0x760/0x1300 fs/fs-writeback.c:2129
generic_update_time+0x26a/0x450 fs/inode.c:1651
update_time fs/inode.c:1667 [inline]
file_update_time+0x390/0x640 fs/inode.c:1877
ext4_page_mkwrite+0x1fe/0x1430 fs/ext4/inode.c:6169
do_page_mkwrite+0x14e/0x520 mm/memory.c:2388
do_shared_fault mm/memory.c:3717 [inline]
do_fault mm/memory.c:3756 [inline]
handle_pte_fault mm/memory.c:3983 [inline]
__handle_mm_fault+0x2a0a/0x4350 mm/memory.c:4107
handle_mm_fault+0x53e/0xc80 mm/memory.c:4144
__do_page_fault+0x620/0xe50 arch/x86/mm/fault.c:1395
do_page_fault+0xf6/0x7a4 arch/x86/mm/fault.c:1470
page_fault+0x1e/0x30 arch/x86/entry/entry_64.S:1161
RIP: 0033:0x405947
Code: 00 00 00 48 83 ec 08 48 8b 15 15 a7 52 00 48 8b 05 06 a7 52 00 48 39
d0 48 8d 8a 00 00 00 01 72 17 48 39 c8 73 12 48 8d 50 04 <89> 38 48 89 15
e8 a6 52 00 48 83 c4 08 c3 48 89 c6 bf 58 bf 4b 00
RSP: 002b:0000000000a3fc10 EFLAGS: 00010287
RAX: 0000001b2ca20000 RBX: 0000000000000003 RCX: 0000001b2da20000
RDX: 0000001b2ca20004 RSI: 0000000000a3f9d0 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000013
R10: 0000000000000075 R11: 0000000000000246 R12: 0000000000000005
R13: 00000000000d23f0 R14: 00000000000000b7 R15: badc0ffeebadface
---
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#bug-status-tracking for how to communicate with
syzbot.
syzbot
Sep 6, 2019, 7:48:06 PM9/6/19
to syzkaller-upst...@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.
Reply all
Reply to author
Forward
0 new messages