[v5.15] WARNING: ODEBUG bug in __do_softirq

5 views
Skip to first unread message

syzbot

unread,
May 14, 2023, 1:49:01 PM5/14/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: b0ece631f84a Linux 5.15.111
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12226a26280000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e93479ceb1e500
dashboard link: https://syzkaller.appspot.com/bug?extid=9cbb926899917345ca6c
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1250ee06280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13739ebe280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4dbb092b5601/disk-b0ece631.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5fe7e3edcf9b/vmlinux-b0ece631.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b2e75f47bfb/bzImage-b0ece631.xz

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

------------[ cut here ]------------
ODEBUG: free active (active state 1) object type: rcu_head hint: 0x0
WARNING: CPU: 1 PID: 0 at lib/debugobjects.c:511 debug_print_object lib/debugobjects.c:508 [inline]
WARNING: CPU: 1 PID: 0 at lib/debugobjects.c:511 __debug_check_no_obj_freed lib/debugobjects.c:1015 [inline]
WARNING: CPU: 1 PID: 0 at lib/debugobjects.c:511 debug_check_no_obj_freed+0x451/0x610 lib/debugobjects.c:1046
Modules linked in:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.111-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
RIP: 0010:debug_print_object lib/debugobjects.c:508 [inline]
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:1015 [inline]
RIP: 0010:debug_check_no_obj_freed+0x451/0x610 lib/debugobjects.c:1046
Code: 74 08 48 89 ef e8 3f 71 be fd 48 8b 13 4c 8b 45 00 48 c7 c7 80 64 d8 8a 48 c7 c6 a0 61 d8 8a 44 89 f1 4d 89 f9 e8 ef ee 40 fd <0f> 0b 48 ba 00 00 00 00 00 fc ff df 4c 8b 74 24 38 ff 05 80 0c d9
RSP: 0018:ffffc90000dd0ab8 EFLAGS: 00010246
RAX: 530f0fd993cc6a00 RBX: ffffffff8ad864f8 RCX: ffff88813fe78000
RDX: 0000000000000101 RSI: 0000000000000101 RDI: 0000000000000000
RBP: ffffffff8a8bffc0 R08: ffffffff8166341c R09: fffff520001ba099
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffffff8a8bffc0
R13: ffff88807a87e870 R14: 0000000000000001 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f550eba31f8 CR3: 0000000072e5c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
slab_free_hook mm/slub.c:1680 [inline]
slab_free_freelist_hook+0x86/0x160 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kfree+0xf1/0x270 mm/slub.c:4559
rcu_do_batch kernel/rcu/tree.c:2510 [inline]
rcu_core+0xa15/0x1650 kernel/rcu/tree.c:2750
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
invoke_softirq kernel/softirq.c:432 [inline]
__irq_exit_rcu+0x155/0x240 kernel/softirq.c:636
irq_exit_rcu+0x5/0x20 kernel/softirq.c:648
sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1096
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:22 [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:132 [inline]
RIP: 0010:acpi_safe_halt drivers/acpi/processor_idle.c:110 [inline]
RIP: 0010:acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:570
Code: 40 5c f7 48 83 e3 08 0f 85 0a 01 00 00 4c 8d 74 24 20 e8 e4 ac 62 f7 0f 1f 44 00 00 e8 6a 3c 5c f7 0f 00 2d 03 ae be 00 fb f4 <4c> 89 f3 48 c1 eb 03 42 80 3c 3b 00 74 08 4c 89 f7 e8 db 97 a5 f7
RSP: 0018:ffffc90000d67b00 EFLAGS: 000002d3
RAX: ffffffff8a23a776 RBX: 0000000000000000 RCX: ffff88813fe78000
RDX: 0000000000000000 RSI: ffffffff8a8afb60 RDI: ffffffff8ad85bc0
RBP: ffffc90000d67b90 R08: ffffffff81865480 R09: ffffed1027fcf001
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920001acf60
R13: ffff8881462bf004 R14: ffffc90000d67b20 R15: dffffc0000000000
acpi_idle_enter+0x352/0x4f0 drivers/acpi/processor_idle.c:705
cpuidle_enter_state+0x521/0xef0 drivers/cpuidle/cpuidle.c:237
cpuidle_enter+0x59/0x90 drivers/cpuidle/cpuidle.c:351
call_cpuidle kernel/sched/idle.c:158 [inline]
cpuidle_idle_call kernel/sched/idle.c:239 [inline]
do_idle+0x3e4/0x670 kernel/sched/idle.c:306
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:403
start_secondary+0x371/0x500 arch/x86/kernel/smpboot.c:270
secondary_startup_64_no_verify+0xb1/0xbb
</TASK>
----------------
Code disassembly (best guess):
0: 40 5c rex pop %rsp
2: f7 48 83 e3 08 0f 85 testl $0x850f08e3,-0x7d(%rax)
9: 0a 01 or (%rcx),%al
b: 00 00 add %al,(%rax)
d: 4c 8d 74 24 20 lea 0x20(%rsp),%r14
12: e8 e4 ac 62 f7 callq 0xf762acfb
17: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
1c: e8 6a 3c 5c f7 callq 0xf75c3c8b
21: 0f 00 2d 03 ae be 00 verw 0xbeae03(%rip) # 0xbeae2b
28: fb sti
29: f4 hlt
* 2a: 4c 89 f3 mov %r14,%rbx <-- trapping instruction
2d: 48 c1 eb 03 shr $0x3,%rbx
31: 42 80 3c 3b 00 cmpb $0x0,(%rbx,%r15,1)
36: 74 08 je 0x40
38: 4c 89 f7 mov %r14,%rdi
3b: e8 db 97 a5 f7 callq 0xf7a5981b


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

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jun 15, 2023, 1:31:32 PM6/15/23
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:

commit cff0af3d1364b6f3a841ac89d30321610961e4d0
Author: Peilin Ye <peil...@bytedance.com>
Date: Mon May 29 19:52:55 2023 +0000

net/sched: sch_ingress: Only create under TC_H_INGRESS

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10255d9d280000
start commit: b0ece631f84a Linux 5.15.111
git tree: linux-5.15.y
If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: net/sched: sch_ingress: Only create under TC_H_INGRESS

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages