From: syzbot <syzbot+29d3a3b4d86c8136ad9e@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, frederic@kernel.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
peterz@infradead.org, sathyanarayanan.kuppuswamy@linux.intel.com,
steven.price@arm.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: [syzbot] WARNING in cpuset_attach
Date: Wed, 24 Aug 2022 09:36:32 -0700 [thread overview]
Message-ID: <0000000000009ebf5605e6ff48d5@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: c40e8341e3b3 Merge tag 'cgroup-for-6.0-rc2-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167bc60b080000
kernel config: https://syzkaller.appspot.com/x/.config?x=911efaff115942bb
dashboard link: https://syzkaller.appspot.com/bug?extid=29d3a3b4d86c8136ad9e
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
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+29d3a3b4d86c8136ad9e@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3684 at kernel/cpu.c:347 lockdep_assert_cpus_held kernel/cpu.c:347 [inline]
WARNING: CPU: 0 PID: 3684 at kernel/cpu.c:347 lockdep_assert_cpus_held+0xbd/0xe0 kernel/cpu.c:336
Modules linked in:
CPU: 0 PID: 3684 Comm: kvm-nx-lpage-re Not tainted 6.0.0-rc2-syzkaller-00054-gc40e8341e3b3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:lockdep_assert_cpus_held kernel/cpu.c:347 [inline]
RIP: 0010:lockdep_assert_cpus_held+0xbd/0xe0 kernel/cpu.c:336
Code: e8 38 0c 34 00 be ff ff ff ff 48 c7 c7 70 64 e3 8b e8 37 71 37 08 31 ff 89 c3 89 c6 e8 dc 08 34 00 85 db 75 d5 e8 13 0c 34 00 <0f> 0b eb cc 48 c7 c7 44 66 de 8d e8 d3 73 80 00 e9 62 ff ff ff 48
RSP: 0018:ffffc90004777c28 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88801f243b00 RSI: ffffffff8147ff0d RDI: 0000000000000005
RBP: ffff88814b0a4800 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90004777de0
R13: ffffffff8bfdc2a0 R14: 1ffff920008eef8c R15: ffffc90004777e04
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020833000 CR3: 000000001bddc000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
cpuset_attach+0x92/0x520 kernel/cgroup/cpuset.c:2292
cgroup_migrate_execute+0xbc7/0x1220 kernel/cgroup/cgroup.c:2584
cgroup_attach_task+0x416/0x7c0 kernel/cgroup/cgroup.c:2875
cgroup_attach_task_all+0xde/0x140 kernel/cgroup/cgroup-v1.c:70
kvm_vm_worker_thread+0xdd/0x5a0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:5979
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@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2022-08-24 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 16:36 syzbot [this message]
2022-08-24 20:32 ` [syzbot] WARNING in cpuset_attach syzbot
2022-08-25 8:38 ` [PATCH] cgroup: Add missing cpus_read_lock() to cgroup_attach_task_all() Tetsuo Handa
2022-08-25 17:44 ` Tejun Heo
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=0000000000009ebf5605e6ff48d5@google.com \
--to=syzbot+29d3a3b4d86c8136ad9e@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=steven.price@arm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.