The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+9ae8e7884e451eaed5b4@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	 tao1.yu@intel.com
Subject: Re: [syzbot] [dri?] [usb?] KASAN: slab-out-of-bounds Read in drm_property_add_enum
Date: Wed, 19 Aug 2026 00:26:02 -0700	[thread overview]
Message-ID: <6a855a8a.c8649fcc.3bb87.000e.GAE@google.com> (raw)
In-Reply-To: <9839aa8d-3a90-4ac1-952a-7763d833a6f8n@googlegroups.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+9ae8e7884e451eaed5b4@syzkaller.appspotmail.com
Tested-by: syzbot+9ae8e7884e451eaed5b4@syzkaller.appspotmail.com

Tested on:

commit:         0d5a4a96 drm/gud: validate TV mode names before creati..
git tree:       https://github.com/yutao-intel/linux.git fix-dri
console output: https://syzkaller.appspot.com/x/log.txt?x=128d9679580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e4131490469a78a3
dashboard link: https://syzkaller.appspot.com/bug?extid=9ae8e7884e451eaed5b4
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
userspace arch: i386

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2026-08-19  7:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9839aa8d-3a90-4ac1-952a-7763d833a6f8n@googlegroups.com>
2026-08-19  7:26 ` syzbot [this message]
     [not found] <06f5b85d-47c0-4d00-a25d-e18b3950701bn@googlegroups.com>
2026-08-19  6:56 ` [syzbot] [dri?] [usb?] KASAN: slab-out-of-bounds Read in drm_property_add_enum syzbot
     [not found] <ba7a07cf-e8e9-4f55-8edf-48c994c52a79n@googlegroups.com>
2026-08-19  6:27 ` syzbot
     [not found] <97256979-906c-4397-b3e8-a83762ce6b58n@googlegroups.com>
2026-08-19  6:21 ` syzbot
2026-08-19  0:44 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=6a855a8a.c8649fcc.3bb87.000e.GAE@google.com \
    --to=syzbot+9ae8e7884e451eaed5b4@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tao1.yu@intel.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