From: syzbot <syzbot+0d7a3627fb6a42cf0863@syzkaller.appspotmail.com>
To: airlied@gmail.com, airlied@linux.ie, daniel.vetter@ffwll.ch,
daniel.vetter@intel.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
maarten.lankhorst@linux.intel.com, melissa.srw@gmail.com,
mripard@kernel.org, syzkaller-bugs@googlegroups.com,
tzimmermann@suse.de
Subject: Re: [syzbot] [dri?] divide error in drm_mode_convert_to_umode
Date: Mon, 12 Feb 2024 04:02:01 -0800 [thread overview]
Message-ID: <000000000000a8616906112e0b4b@google.com> (raw)
In-Reply-To: <000000000000587e0f06112cd973@google.com>
syzbot has bisected this issue to:
commit ea40d7857d5250e5400f38c69ef9e17321e9c4a2
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Fri Oct 9 23:21:56 2020 +0000
drm/vkms: fbdev emulation support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14426df4180000
start commit: 445a555e0623 Add linux-next specific files for 20240209
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16426df4180000
console output: https://syzkaller.appspot.com/x/log.txt?x=12426df4180000
kernel config: https://syzkaller.appspot.com/x/.config?x=85aa3388229f9ea9
dashboard link: https://syzkaller.appspot.com/bug?extid=0d7a3627fb6a42cf0863
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17d4bd48180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=106ae642180000
Reported-by: syzbot+0d7a3627fb6a42cf0863@syzkaller.appspotmail.com
Fixes: ea40d7857d52 ("drm/vkms: fbdev emulation support")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-02-12 12:02 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 [this message]
2024-02-12 12:07 ` [PATCH] Test divide err in drm Edward Adam Davis
2024-02-12 12:30 ` [syzbot] [dri?] divide error in drm_mode_convert_to_umode syzbot
2025-01-05 2:39 ` 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=000000000000a8616906112e0b4b@google.com \
--to=syzbot+0d7a3627fb6a42cf0863@syzkaller.appspotmail.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tzimmermann@suse.de \
/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.