From: syzbot <syzbot+b637b6748f2b5dc92271@syzkaller.appspotmail.com>
To: Henry.Wang@arm.com, bigeasy@linutronix.de,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
longpeng2@huawei.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, vschneid@redhat.com
Subject: [syzbot] usb-testing boot error: BUG: corrupted list in pick_next_task_fair
Date: Mon, 22 Aug 2022 01:18:32 -0700 [thread overview]
Message-ID: <000000000000ec8f5c05e6d0175f@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 568035b01cfb Linux 6.0-rc1
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=13cc503d080000
kernel config: https://syzkaller.appspot.com/x/.config?x=3cb39b084894e9a5
dashboard link: https://syzkaller.appspot.com/bug?extid=b637b6748f2b5dc92271
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b637b6748f2b5dc92271@syzkaller.appspotmail.com
list_del corruption. next->prev should be ffff88810b71d628, but was ffff000000000000. (next=ffff88810e7380a8)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:62!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 19 Comm: ksoftirqd/1 Not tainted 6.0.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:__list_del_entry_valid.cold+0x70/0x72 lib/list_debug.c:62
Code: fc ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 40 b4 62 86 e8 c7 1e fc ff 0f 0b 4c 89 e9 48 89 ee 48 c7 c7 80 b5 62 86 e8 b3 1e fc ff <0f> 0b 83 c3 01 b8 ff ff 37 00 89 1d 22 2a ce 05 48 c1 e0 2a 65 48
RSP: 0000:ffffc9000014fd58 EFLAGS: 00010082
RAX: 000000000000006d RBX: ffff8881f6937b00 RCX: 0000000000000000
RDX: ffff888100365580 RSI: ffffffff812c97e8 RDI: fffff52000029f9d
RBP: ffff88810b71d628 R08: 000000000000006d R09: 0000000000000000
R10: 0000000080000002 R11: 000000000000004e R12: ffff8881f69385e8
R13: ffff88810e7380a8 R14: ffff8881f69385e8 R15: ffffc9000014fe30
FS: 0000000000000000(0000) GS:ffff8881f6900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000007825000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry include/linux/list.h:134 [inline]
list_move include/linux/list.h:217 [inline]
pick_next_task_fair+0x170/0xf80 kernel/sched/fair.c:7468
__pick_next_task kernel/sched/core.c:5804 [inline]
pick_next_task kernel/sched/core.c:6313 [inline]
__schedule+0x3a3/0x26f0 kernel/sched/core.c:6458
schedule+0xda/0x1b0 kernel/sched/core.c:6570
smpboot_thread_fn+0x2eb/0x9c0 kernel/smpboot.c:160
kthread+0x2ea/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid.cold+0x70/0x72 lib/list_debug.c:62
Code: fc ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 40 b4 62 86 e8 c7 1e fc ff 0f 0b 4c 89 e9 48 89 ee 48 c7 c7 80 b5 62 86 e8 b3 1e fc ff <0f> 0b 83 c3 01 b8 ff ff 37 00 89 1d 22 2a ce 05 48 c1 e0 2a 65 48
RSP: 0000:ffffc9000014fd58 EFLAGS: 00010082
RAX: 000000000000006d RBX: ffff8881f6937b00 RCX: 0000000000000000
RDX: ffff888100365580 RSI: ffffffff812c97e8 RDI: fffff52000029f9d
RBP: ffff88810b71d628 R08: 000000000000006d R09: 0000000000000000
R10: 0000000080000002 R11: 000000000000004e R12: ffff8881f69385e8
R13: ffff88810e7380a8 R14: ffff8881f69385e8 R15: ffffc9000014fe30
FS: 0000000000000000(0000) GS:ffff8881f6900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000007825000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2022-08-22 8:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000ec8f5c05e6d0175f@google.com \
--to=syzbot+b637b6748f2b5dc92271@syzkaller.appspotmail.com \
--cc=Henry.Wang@arm.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox