From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+087b7effddeec0697c66@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in kthread_bind_mask
Date: Mon, 10 Jul 2023 14:49:44 -0700 [thread overview]
Message-ID: <ZKx8+B3gI9/1g5A3@google.com> (raw)
In-Reply-To: <0000000000005ca92705d877448c@google.com>
Trimmed the Cc list to avoid annoying folks with my thread necromancy.
On Sun, Feb 20, 2022, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: c5d9ae265b10 Merge tag 'for-linus' of git://git.kernel.org..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11daf74a700000
> kernel config: https://syzkaller.appspot.com/x/.config?x=da674567f7b6043d
> dashboard link: https://syzkaller.appspot.com/bug?extid=087b7effddeec0697c66
> 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+087b7effddeec0697c66@syzkaller.appspotmail.com
>
> BTRFS info (device loop3): disk space caching is enabled
> BTRFS info (device loop3): has skinny extents
> ------------[ cut here ]------------
Dropping the "kvm" label as this isn't a KVM bug, but rather something in either
workqueues or sched that KVM often triggers through its use of alloc_workqueue().
#syz set subsystems: kernel
next prev parent reply other threads:[~2023-07-10 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 18:27 [syzbot] WARNING in kthread_bind_mask syzbot
2022-02-21 14:23 ` David Sterba
2022-02-22 1:51 ` Zhang, Qiang1
2023-07-10 21:49 ` Sean Christopherson [this message]
2023-07-11 4:01 ` Z qiang
2023-07-11 21:29 ` 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=ZKx8+B3gI9/1g5A3@google.com \
--to=seanjc@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+087b7effddeec0697c66@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 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.