From: syzbot <syzbot+8fe2d362af0e1cba8735@syzkaller.appspotmail.com>
To: agordeev@linux.ibm.com, akrowiak@linux.ibm.com,
benjamin.tissoires@redhat.com, clg@redhat.com,
davem@davemloft.net, david.rheinsberg@gmail.com,
edumazet@google.com, jikos@kernel.org, kuba@kernel.org,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
mjrosato@linux.ibm.com, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [input?] INFO: task hung in uhid_char_release
Date: Tue, 29 Aug 2023 10:28:25 -0700 [thread overview]
Message-ID: <00000000000068345606041323fc@google.com> (raw)
In-Reply-To: <000000000000c329d505fed78c74@google.com>
syzbot has bisected this issue to:
commit bf48961f6f48e3b7eb80c3e179207e9f4e4cd660
Author: Tony Krowiak <akrowiak@linux.ibm.com>
Date: Tue May 30 22:35:37 2023 +0000
s390/vfio-ap: realize the VFIO_DEVICE_SET_IRQS ioctl
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155eba2fa80000
start commit: bde7f150276b Merge tag 'pm-6.5-rc2' of git://git.kernel.or..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=175eba2fa80000
console output: https://syzkaller.appspot.com/x/log.txt?x=135eba2fa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=6d0f369ef5fb88c9
dashboard link: https://syzkaller.appspot.com/bug?extid=8fe2d362af0e1cba8735
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=124711b6a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=178c5a92a80000
Reported-by: syzbot+8fe2d362af0e1cba8735@syzkaller.appspotmail.com
Fixes: bf48961f6f48 ("s390/vfio-ap: realize the VFIO_DEVICE_SET_IRQS ioctl")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-29 17:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 3:16 [syzbot] [input?] INFO: task hung in uhid_char_release syzbot
2023-08-29 17:28 ` syzbot [this message]
2023-08-29 18:56 ` Matthew Rosato
2025-09-21 3:29 ` [syzbot] [kernel?] " syzbot
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=00000000000068345606041323fc@google.com \
--to=syzbot+8fe2d362af0e1cba8735@syzkaller.appspotmail.com \
--cc=agordeev@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=benjamin.tissoires@redhat.com \
--cc=clg@redhat.com \
--cc=davem@davemloft.net \
--cc=david.rheinsberg@gmail.com \
--cc=edumazet@google.com \
--cc=jikos@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).