From: syzbot <syzbot+f6cb41c144427dc0796a@syzkaller.appspotmail.com>
To: calixte.pernot@grenoble-inp.org, eadavis@qq.com,
gregkh@linuxfoundation.org, jirislaby@kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
npitre@baylibre.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [serial?] general protection fault in vc_deallocate
Date: Tue, 09 Sep 2025 23:21:02 -0700 [thread overview]
Message-ID: <68c118ce.a70a0220.3543fc.000d.GAE@google.com> (raw)
In-Reply-To: <68bf244a.050a0220.192772.0882.GAE@google.com>
syzbot has bisected this issue to:
commit 23743ba64709a9c137c1b928f8b8e00d846af9cc
Author: Calixte Pernot <calixte.pernot@grenoble-inp.org>
Date: Mon Aug 25 12:56:09 2025 +0000
vt: add support for smput/rmput escape codes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16fded62580000
start commit: 3e8e5822146b Add linux-next specific files for 20250908
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=15fded62580000
console output: https://syzkaller.appspot.com/x/log.txt?x=11fded62580000
kernel config: https://syzkaller.appspot.com/x/.config?x=69cfefa929ab96f7
dashboard link: https://syzkaller.appspot.com/bug?extid=f6cb41c144427dc0796a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17230934580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15984642580000
Reported-by: syzbot+f6cb41c144427dc0796a@syzkaller.appspotmail.com
Fixes: 23743ba64709 ("vt: add support for smput/rmput escape codes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-09-10 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 18:45 [syzbot] [serial?] general protection fault in vc_deallocate syzbot
2025-09-09 0:51 ` [PATCH Next] vt: move vc_saved_screen to within tty allocated judgment Edward Adam Davis
2025-09-09 6:35 ` Jiri Slaby
2025-09-10 6:21 ` syzbot [this message]
2025-09-10 6:48 ` [syzbot] [serial?] general protection fault in vc_deallocate Jiri Slaby
2025-09-10 7:20 ` 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=68c118ce.a70a0220.3543fc.000d.GAE@google.com \
--to=syzbot+f6cb41c144427dc0796a@syzkaller.appspotmail.com \
--cc=calixte.pernot@grenoble-inp.org \
--cc=eadavis@qq.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=npitre@baylibre.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