From: syzbot <syzbot+622acb507894a48b2ce9@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
cgroups@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, elic@nvidia.com,
gregkh@linuxfoundation.org, hannes@cmpxchg.org, hawk@kernel.org,
jasowang@redhat.com, jirislaby@kernel.org,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
kuba@kernel.org, len.brown@intel.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-serial@vger.kernel.org, mingo@redhat.com,
mkoutny@suse.com, mst@redhat.com, netdev@vger.kernel.org,
parav@nvidia.com, pavel@ucw.cz, rafael@kernel.org,
rostedt@goodmis.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, tj@kernel.org, yhs@fb.com
Subject: Re: [syzbot] [cgroups?] possible deadlock in console_lock_spinning_enable (5)
Date: Fri, 17 Jan 2025 04:34:03 -0800 [thread overview]
Message-ID: <678a4e3b.050a0220.303755.0005.GAE@google.com> (raw)
In-Reply-To: <0000000000001e66f5061fe3b883@google.com>
syzbot has bisected this issue to:
commit bc0d90ee021f1baecd6aaa010d787eb373aa74dd
Author: Parav Pandit <parav@nvidia.com>
Date: Tue Jan 5 10:32:02 2021 +0000
vdpa: Enable user to query vdpa device info
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1440c2b0580000
start commit: 619f0b6fad52 Merge tag 'seccomp-v6.13-rc8' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1640c2b0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1240c2b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d1cb4a1f148c0861
dashboard link: https://syzkaller.appspot.com/bug?extid=622acb507894a48b2ce9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=175029df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f29a18580000
Reported-by: syzbot+622acb507894a48b2ce9@syzkaller.appspotmail.com
Fixes: bc0d90ee021f ("vdpa: Enable user to query vdpa device info")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-01-17 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 16:39 [syzbot] [serial?] possible deadlock in console_lock_spinning_enable (5) syzbot
2024-10-03 20:37 ` [syzbot] [cgroups?] " syzbot
2025-01-22 10:35 ` Hillf Danton
2025-01-22 10:54 ` syzbot
2025-01-17 12:34 ` syzbot [this message]
2025-01-21 18:29 ` Michal Koutný
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=678a4e3b.050a0220.303755.0005.GAE@google.com \
--to=syzbot+622acb507894a48b2ce9@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=elic@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=jirislaby@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=yhs@fb.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.