From: syzbot <syzbot+52cf91760dcb1dac6376@syzkaller.appspotmail.com>
To: elic@nvidia.com, gregkh@linuxfoundation.org, jasowang@redhat.com,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, mst@redhat.com, parav@nvidia.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [serial?] possible deadlock in tty_buffer_flush (3)
Date: Sun, 19 Jan 2025 22:18:03 -0800 [thread overview]
Message-ID: <678dea9b.050a0220.303755.0068.GAE@google.com> (raw)
In-Reply-To: <0000000000004228140621a87013@google.com>
syzbot has bisected this issue to:
commit a3c06ae158dd6fa8336157c31d9234689d068d02
Author: Parav Pandit <parav@nvidia.com>
Date: Tue Jan 5 10:32:03 2021 +0000
vdpa_sim_net: Add support for user supported devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=101452b0580000
start commit: 595523945be0 Merge tag 'devicetree-fixes-for-6.13-2' of gi..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=121452b0580000
console output: https://syzkaller.appspot.com/x/log.txt?x=141452b0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d1cb4a1f148c0861
dashboard link: https://syzkaller.appspot.com/bug?extid=52cf91760dcb1dac6376
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=164091f8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17903fc4580000
Reported-by: syzbot+52cf91760dcb1dac6376@syzkaller.appspotmail.com
Fixes: a3c06ae158dd ("vdpa_sim_net: Add support for user supported devices")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-01-20 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 4:46 [syzbot] [serial?] possible deadlock in tty_buffer_flush (3) syzbot
2024-12-31 22:34 ` syzbot
2025-01-18 19:12 ` syzbot
2025-01-20 6:18 ` 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=678dea9b.050a0220.303755.0068.GAE@google.com \
--to=syzbot+52cf91760dcb1dac6376@syzkaller.appspotmail.com \
--cc=elic@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mst@redhat.com \
--cc=parav@nvidia.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