All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f6cb41c144427dc0796a@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [serial?] general protection fault in vc_deallocate
Date: Mon, 08 Sep 2025 17:34:04 -0700	[thread overview]
Message-ID: <68bf75fc.a00a0220.eb3d.0037.GAE@google.com> (raw)
In-Reply-To: <tencent_31282D116C4C9408EAF6ED0ECC4478466E0A@qq.com>

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:         3e8e5822 Add linux-next specific files for 20250908
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14fdf562580000
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
patch:          https://syzkaller.appspot.com/x/patch.diff?x=170cd87c580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2025-09-09  0:34 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 [this message]
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

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=68bf75fc.a00a0220.eb3d.0037.GAE@google.com \
    --to=syzbot+f6cb41c144427dc0796a@syzkaller.appspotmail.com \
    --cc=eadavis@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.