From: syzbot <syzbot+2ab700fe1829880a2ec6@syzkaller.appspotmail.com>
To: cgroups@vger.kernel.org, hannes@cmpxchg.org,
hverkuil-cisco@xs4all.nl, hverkuil@xs4all.nl,
linux-kernel@vger.kernel.org, lizefan.x@bytedance.com,
mchehab@kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org
Subject: Re: [syzbot] [cgroups?] possible deadlock in static_key_slow_inc (3)
Date: Thu, 08 Jun 2023 20:17:24 -0700 [thread overview]
Message-ID: <000000000000d1565005fda9cef1@google.com> (raw)
In-Reply-To: <000000000000bd448705fda123f5@google.com>
syzbot has bisected this issue to:
commit eb1d969203eb8212741751f88dcf5cb56bb11830
Author: Hans Verkuil <hverkuil@xs4all.nl>
Date: Fri Oct 21 12:21:25 2022 +0000
media: vivid: fix control handler mutex deadlock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16af9d95280000
start commit: 5f63595ebd82 Merge tag 'input-for-v6.4-rc5' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=15af9d95280000
console output: https://syzkaller.appspot.com/x/log.txt?x=11af9d95280000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c980bfe8b399968
dashboard link: https://syzkaller.appspot.com/bug?extid=2ab700fe1829880a2ec6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142e0463280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a32add280000
Reported-by: syzbot+2ab700fe1829880a2ec6@syzkaller.appspotmail.com
Fixes: eb1d969203eb ("media: vivid: fix control handler mutex deadlock")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-06-09 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 16:56 [syzbot] [cgroups?] possible deadlock in static_key_slow_inc (3) syzbot
2023-06-09 3:17 ` syzbot [this message]
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=000000000000d1565005fda9cef1@google.com \
--to=syzbot+2ab700fe1829880a2ec6@syzkaller.appspotmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mchehab@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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