[<prev] [next>] [day] [month] [year] [list]
Message-ID: <0000000000004bffef05e5df7207@google.com>
Date: Wed, 10 Aug 2022 02:12:21 -0700
From: syzbot <syzbot+0f36653d0d34001e0b43@...kaller.appspotmail.com>
To: akpm@...ux-foundation.org, bigeasy@...utronix.de,
bpf@...r.kernel.org, brauner@...nel.org, david@...hat.com,
ebiederm@...ssion.com, linux-kernel@...r.kernel.org,
linux-next@...r.kernel.org, luto@...nel.org, sfr@...b.auug.org.au,
syzkaller-bugs@...glegroups.com, tglx@...utronix.de
Subject: [syzbot] linux-next boot error: WARNING in copy_process
Hello,
syzbot found the following issue on:
HEAD commit: bc6c6584ffb2 Add linux-next specific files for 20220810
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=109b7021080000
kernel config: https://syzkaller.appspot.com/x/.config?x=5784be4315a4403b
dashboard link: https://syzkaller.appspot.com/bug?extid=0f36653d0d34001e0b43
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+0f36653d0d34001e0b43@...kaller.appspotmail.com
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(!p->softirqs_enabled)
WARNING: CPU: 0 PID: 1047 at kernel/fork.c:2115 copy_process+0x36c9/0x7120 kernel/fork.c:2115
Modules linked in:
CPU: 0 PID: 1047 Comm: kworker/u4:5 Not tainted 5.19.0-next-20220810-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Workqueue: events_unbound call_usermodehelper_exec_work
RIP: 0010:copy_process+0x36c9/0x7120 kernel/fork.c:2115
Code: 0c 31 ff 89 de e8 a7 00 35 00 85 db 0f 85 c3 d7 ff ff e8 da 03 35 00 48 c7 c6 c0 11 eb 89 48 c7 c7 00 12 eb 89 e8 68 3a f3 07 <0f> 0b e9 a4 d7 ff ff e8 bb 03 35 00 0f 0b e8 b4 03 35 00 0f 0b e8
RSP: 0000:ffffc90005187938 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88801f015880 RSI: ffffffff8161f1f8 RDI: fffff52000a30f19
RBP: ffffc90005187ac8 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000001 R12: ffff88802017002c
R13: ffff888020170000 R14: ffffc90005187c10 R15: 0000000000808100
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000bc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kernel_clone+0xe7/0xab0 kernel/fork.c:2675
user_mode_thread+0xad/0xe0 kernel/fork.c:2744
call_usermodehelper_exec_work kernel/umh.c:174 [inline]
call_usermodehelper_exec_work+0xcc/0x180 kernel/umh.c:160
process_one_work+0x991/0x1610 kernel/workqueue.c:2289
worker_thread+0x665/0x1080 kernel/workqueue.c:2436
kthread+0x2e4/0x3a0 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
---
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@...glegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
Powered by blists - more mailing lists