From: syzbot <syzbot+398e17b61dab22cc56bc@syzkaller.appspotmail.com>
To: airlied@gmail.com, airlied@linux.ie, christian.koenig@amd.com,
daniel.vetter@ffwll.ch, daniel.vetter@intel.com,
daniel@ffwll.ch, dri-devel@lists.freedesktop.org,
hdanton@sina.com, linaro-mm-sig-bounces@lists.linaro.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, sumit.semwal@linaro.org,
syzkaller-bugs@googlegroups.com, tzimmermann@suse.de
Subject: Re: [syzbot] [dri?] kernel BUG in vmf_insert_pfn_prot (2)
Date: Wed, 08 Nov 2023 06:46:04 -0800 [thread overview]
Message-ID: <00000000000089f4110609a525b2@google.com> (raw)
In-Reply-To: <0000000000002a4da90603a5cbbf@google.com>
syzbot has bisected this issue to:
commit 45d9c8dde4cd8589f9180309ec60f0da2ce486e4
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date: Thu Aug 12 13:14:12 2021 +0000
drm/vgem: use shmem helpers
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=126094df680000
start commit: d2f51b3516da Merge tag 'rtc-6.7' of git://git.kernel.org/p..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=116094df680000
console output: https://syzkaller.appspot.com/x/log.txt?x=166094df680000
kernel config: https://syzkaller.appspot.com/x/.config?x=1ffa1cec3b40f3ce
dashboard link: https://syzkaller.appspot.com/bug?extid=398e17b61dab22cc56bc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16344918e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156bb2c0e80000
Reported-by: syzbot+398e17b61dab22cc56bc@syzkaller.appspotmail.com
Fixes: 45d9c8dde4cd ("drm/vgem: use shmem helpers")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-11-08 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 7:01 [syzbot] [dri?] kernel BUG in vmf_insert_pfn_prot (2) syzbot
2023-11-06 23:25 ` syzbot
2023-11-08 14:46 ` syzbot [this message]
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=00000000000089f4110609a525b2@google.com \
--to=syzbot+398e17b61dab22cc56bc@syzkaller.appspotmail.com \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdanton@sina.com \
--cc=linaro-mm-sig-bounces@lists.linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sumit.semwal@linaro.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.