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: Wed, 10 Sep 2025 00:20:03 -0700 [thread overview]
Message-ID: <68c126a3.050a0220.3c6139.001b.GAE@google.com> (raw)
In-Reply-To: <39724768-c8e2-4efa-ac08-cce3d30414b8@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+f6cb41c144427dc0796a@syzkaller.appspotmail.com
Tested-by: syzbot+f6cb41c144427dc0796a@syzkaller.appspotmail.com
Tested on:
commit: 55196010 vt: move vc_saved_screen to within tty alloca..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git/ tty-fix
console output: https://syzkaller.appspot.com/x/log.txt?x=159bed62580000
kernel config: https://syzkaller.appspot.com/x/.config?x=69cfefa929ab96f7
dashboard link: https://syzkaller.appspot.com/bug?extid=f6cb41c144427dc0796a
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2025-09-10 7:20 UTC|newest]
Thread overview: 8+ 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:10 ` Edward Adam Davis
2025-09-09 0:34 ` 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] [serial?] general protection fault in vc_deallocate syzbot
2025-09-10 6:48 ` Jiri Slaby
2025-09-10 7:20 ` 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=68c126a3.050a0220.3c6139.001b.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