WARNING: ODEBUG bug in __run_timers

7 views
Skip to first unread message

syzbot

unread,
Sep 24, 2020, 2:18:16 PM9/24/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 325d0eab Merge branch 'akpm' (patches from Andrew)
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167e8f8b900000
kernel config: https://syzkaller.appspot.com/x/.config?x=b12e84189082991c
dashboard link: https://syzkaller.appspot.com/bug?extid=834859f07052845f24f9
compiler: gcc (GCC) 10.1.0-syz 20200507
userspace arch: i386
CC: [ak...@linux-foundation.org b...@alien8.de h...@zytor.com linux-...@vger.kernel.org lu...@kernel.org mi...@redhat.com tg...@linutronix.de x...@kernel.org]

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

------------[ cut here ]------------
ODEBUG: deactivate not available (active state 0) object type: timer_list hint: mrp_join_timer+0x0/0xc0 net/802/mrp.c:483
WARNING: CPU: 0 PID: 25161 at lib/debugobjects.c:485 debug_print_object+0x16e/0x250 lib/debugobjects.c:485
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 25161 Comm: syz-executor.1 Not tainted 5.9.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x198/0x1fd lib/dump_stack.c:118
panic+0x382/0x7fb kernel/panic.c:231
__warn.cold+0x20/0x4b kernel/panic.c:600
report_bug+0x1bd/0x210 lib/bug.c:198
handle_bug+0x38/0x90 arch/x86/kernel/traps.c:234
exc_invalid_op+0x14/0x40 arch/x86/kernel/traps.c:254
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:536
RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:485
Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd 80 c1 d8 88 4c 89 ee 48 c7 c7 e0 b6 d8 88 e8 c4 d5 82 fd <0f> 0b 83 05 15 ab 95 07 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3
RSP: 0018:ffffc90000007ce0 EFLAGS: 00010086
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000000
RDX: ffff888055c98140 RSI: ffffffff815f5a85 RDI: fffff52000000f8e
RBP: 0000000000000001 R08: 0000000000000001 R09: ffff8880ae420f8b
R10: 0000000000000000 R11: 0000000000003043 R12: ffffffff8a07dee0
R13: ffffffff88d8bb40 R14: ffffffff81655000 R15: ffff8880a3cad010
debug_object_deactivate lib/debugobjects.c:738 [inline]
debug_object_deactivate+0x1c0/0x300 lib/debugobjects.c:698
debug_timer_deactivate kernel/time/timer.c:732 [inline]
debug_deactivate kernel/time/timer.c:781 [inline]
detach_timer kernel/time/timer.c:826 [inline]
expire_timers kernel/time/timer.c:1447 [inline]
__run_timers.part.0+0x51a/0xaa0 kernel/time/timer.c:1755
__run_timers kernel/time/timer.c:1736 [inline]
run_timer_softirq+0xb3/0x1d0 kernel/time/timer.c:1768
__do_softirq+0x1f8/0xb23 kernel/softirq.c:298
asm_call_on_stack+0xf/0x20 arch/x86/entry/entry_64.S:706
</IRQ>
__run_on_irqstack arch/x86/include/asm/irq_stack.h:22 [inline]
run_on_irqstack_cond arch/x86/include/asm/irq_stack.h:48 [inline]
do_softirq_own_stack+0x9d/0xd0 arch/x86/kernel/irq_64.c:77
invoke_softirq kernel/softirq.c:393 [inline]
__irq_exit_rcu kernel/softirq.c:423 [inline]
irq_exit_rcu+0x235/0x280 kernel/softirq.c:435
sysvec_apic_timer_interrupt+0x51/0xf0 arch/x86/kernel/apic/apic.c:1091
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:581
RIP: 0010:compound_head include/linux/page-flags.h:182 [inline]
RIP: 0010:PageAnon include/linux/page-flags.h:479 [inline]
RIP: 0010:page_remove_rmap+0x40/0x1690 mm/rmap.c:1330
Code: ec 08 e8 23 a2 ca ff 48 89 ef e8 ab de 10 00 4c 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 fc 13 00 00 <4c> 8b 7d 08 31 ff 48 89 eb 4d 89 fe 41 83 e6 01 4c 89 f6 e8 68 9e
RSP: 0018:ffffc90016e7f718 EFLAGS: 00000246
RAX: dffffc0000000000 RBX: 00000000f7c31000 RCX: 0000000000000001
RDX: 1ffffd400049c711 RSI: 0000000000000002 RDI: ffff8880ae436ce0
RBP: ffffea00024e3880 R08: 0000000000000000 R09: ffffffff8d0b79e7
R10: fffffbfff1a16f3c R11: 0000000000000000 R12: 0000000000000000
R13: ffffea00024e3888 R14: dffffc0000000000 R15: 0000000000000000
zap_pte_range mm/memory.c:1093 [inline]
zap_pmd_range mm/memory.c:1197 [inline]
zap_pud_range mm/memory.c:1226 [inline]
zap_p4d_range mm/memory.c:1247 [inline]
unmap_page_range+0xf6b/0x2bf0 mm/memory.c:1268
unmap_single_vma+0x198/0x300 mm/memory.c:1313
unmap_vmas+0x168/0x2e0 mm/memory.c:1345
exit_mmap+0x2b1/0x530 mm/mmap.c:3183
__mmput+0x122/0x470 kernel/fork.c:1076
mmput+0x53/0x60 kernel/fork.c:1097
exit_mm kernel/exit.c:483 [inline]
do_exit+0xa8b/0x29f0 kernel/exit.c:793
do_group_exit+0x125/0x310 kernel/exit.c:903
get_signal+0x428/0x1f00 kernel/signal.c:2757
arch_do_signal+0x82/0x2520 arch/x86/kernel/signal.c:811
exit_to_user_mode_loop kernel/entry/common.c:159 [inline]
exit_to_user_mode_prepare+0x1ae/0x200 kernel/entry/common.c:190
syscall_exit_to_user_mode+0x7e/0x2e0 kernel/entry/common.c:265
__do_fast_syscall_32+0x6c/0x90 arch/x86/entry/common.c:138
do_fast_syscall_32+0x2f/0x70 arch/x86/entry/common.c:160
entry_SYSENTER_compat_after_hwframe+0x4d/0x5c
RIP: 0023:0xf7efd549
Code: Bad RIP value.
RSP: 002b:00000000f54f712c EFLAGS: 00000246 ORIG_RAX: 00000000000000f0
RAX: 0000000000000001 RBX: 0000000008b9bfac RCX: 0000000000000081
RDX: 00000000000f4240 RSI: 0000000008b9bfa0 RDI: 0000000008b9bfac
RBP: 00000000f54f7228 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000

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


---
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,
Dec 19, 2020, 1:17:08 PM12/19/20
to syzkaller-upst...@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