From: syzbot <syzbot+2d4f8693f438d2bd4bdb@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,
javierm@redhat.com, linaro-mm-sig-owner@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, suijingfeng@loongson.cn,
sumit.semwal@linaro.org, syzkaller-bugs@googlegroups.com,
tzimmermann@suse.de, zackr@vmware.com
Subject: Re: [syzbot] kernel BUG in vmf_insert_pfn_prot
Date: Tue, 13 Jun 2023 12:23:34 -0700 [thread overview]
Message-ID: <0000000000006d819905fe07c52f@google.com> (raw)
In-Reply-To: <000000000000fe7dd005cc2d77c0@google.com>
syzbot suspects this issue was fixed by commit:
commit a5b44c4adb1699661d22e5152fb26885f30a2e4c
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date: Mon Mar 20 15:07:44 2023 +0000
drm/fbdev-generic: Always use shadow buffering
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1025ee07280000
start commit: 0326074ff465 Merge tag 'net-next-6.1' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d323d85b1f8a4ed7
dashboard link: https://syzkaller.appspot.com/bug?extid=2d4f8693f438d2bd4bdb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14fd1182880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17567514880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: drm/fbdev-generic: Always use shadow buffering
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-13 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 9:22 [syzbot] kernel BUG in vmf_insert_pfn_prot syzbot
2021-09-18 15:55 ` syzbot
2021-09-18 19:58 ` syzbot
2023-06-13 19:23 ` syzbot [this message]
2023-06-14 7:33 ` Dmitry Vyukov
2023-06-14 7:33 ` Dmitry Vyukov
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=0000000000006d819905fe07c52f@google.com \
--to=syzbot+2d4f8693f438d2bd4bdb@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=javierm@redhat.com \
--cc=linaro-mm-sig-owner@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=suijingfeng@loongson.cn \
--cc=sumit.semwal@linaro.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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 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.