The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+9ae8e7884e451eaed5b4@syzkaller.appspotmail.com>
To: tao1.yu@intel.com
Cc: syzkaller-bugs@googlegroups.com, tao1.yu@intel.com,
	 linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [dri?] [usb?] KASAN: slab-out-of-bounds Read in drm_property_add_enum
Date: Tue, 18 Aug 2026 23:27:31 -0700	[thread overview]
Message-ID: <6a854cd3.f7a79266.2f965f.003a.GAE@google.com> (raw)
In-Reply-To: <ba7a07cf-e8e9-4f55-8edf-48c994c52a79n@googlegroups.com>

> Retry
> #syz test diff --git a/drivers/gpu/drm/gud/gud_connector.c 

I've failed to parse your command.
Did you perhaps forget to provide the branch name, or added an extra ':'?
Please use one of the two supported formats:
1. #syz test
2. #syz test: repo branch-or-commit-hash
Note the lack of ':' in option 1.

> b/drivers/gpu/drm/gud/gud_connector.c index ea0cca58b7c89..8141c3a1e30ad 
> 100644 --- a/drivers/gpu/drm/gud/gud_connector.c +++ 
> b/drivers/gpu/drm/gud/gud_connector.c @@ -396,8 +396,16 @@ static int 
> gud_connector_add_tv_mode(struct gud_device *gdrm, struct drm_connect } 
> num_modes = ret / GUD_CONNECTOR_TV_MODE_NAME_LEN; - for (i = 0; i < 
> num_modes; i++) - modes[i] = &buf[i * GUD_CONNECTOR_TV_MODE_NAME_LEN]; + for 
> (i = 0; i < num_modes; i++) { + char *mode = &buf[i * 
> GUD_CONNECTOR_TV_MODE_NAME_LEN]; + + if (!memchr(mode, '\0', 
> GUD_CONNECTOR_TV_MODE_NAME_LEN)) { + ret = -EIO; + goto free; + } + + 
> modes[i] = mode; + } ret = 
> drm_mode_create_tv_properties_legacy(connector->dev, num_modes, modes); free
> :
> On Wednesday, August 19, 2026 at 2:21:05 PM UTC+8 syzbot wrote:
>
>> Hello,
>>
>> syzbot tried to test the proposed patch but the build/boot failed:
>>
>> failed to apply patch:
>> error: corrupt patch at line 6
>>
>>
>>
>> Tested on:
>>
>> commit: bd5f485f Merge tag 'soc-arm-7.3' of git://git.kernel.o..
>> git tree: upstream
>> kernel config: https://syzkaller.appspot.com/x/.config?x=65bd434865e8f85c
>> dashboard link: 
>> https://syzkaller.appspot.com/bug?extid=9ae8e7884e451eaed5b4
>> compiler: 
>> userspace arch: i386
>> patch: https://syzkaller.appspot.com/x/patch.diff?x=168a7679580000
>>
>>
>
> -- 
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-bugs/ba7a07cf-e8e9-4f55-8edf-48c994c52a79n%40googlegroups.com.

       reply	other threads:[~2026-08-19  6:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ba7a07cf-e8e9-4f55-8edf-48c994c52a79n@googlegroups.com>
2026-08-19  6:27 ` syzbot [this message]
     [not found] <9839aa8d-3a90-4ac1-952a-7763d833a6f8n@googlegroups.com>
2026-08-19  7:26 ` [syzbot] [dri?] [usb?] KASAN: slab-out-of-bounds Read in drm_property_add_enum syzbot
     [not found] <06f5b85d-47c0-4d00-a25d-e18b3950701bn@googlegroups.com>
2026-08-19  6:56 ` 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=6a854cd3.f7a79266.2f965f.003a.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