public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0d7a3627fb6a42cf0863@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [dri?] divide error in drm_mode_convert_to_umode
Date: Mon, 12 Feb 2024 04:30:02 -0800	[thread overview]
Message-ID: <000000000000d3c50a06112e6f7f@google.com> (raw)
In-Reply-To: <tencent_9E786E6C4C2DF96F4097BCEA5AED66CEBC0A@qq.com>

Hello,

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

Reported-and-tested-by: syzbot+0d7a3627fb6a42cf0863@syzkaller.appspotmail.com

Tested on:

commit:         ae00c445 Add linux-next specific files for 20240212
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=154105ec180000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4eb3a27eddb32a14
dashboard link: https://syzkaller.appspot.com/bug?extid=0d7a3627fb6a42cf0863
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=160d0724180000

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

  reply	other threads:[~2024-02-12 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 10:36 [syzbot] [dri?] divide error in drm_mode_convert_to_umode syzbot
2024-02-12 12:02 ` syzbot
2024-02-12 12:07 ` [PATCH] Test divide err in drm Edward Adam Davis
2024-02-12 12:30   ` syzbot [this message]
2025-01-05  2:39 ` [syzbot] [dri?] divide error in drm_mode_convert_to_umode 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=000000000000d3c50a06112e6f7f@google.com \
    --to=syzbot+0d7a3627fb6a42cf0863@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox