From: syzbot <syzbot+17a207d226b8a5fb0fd9@syzkaller.appspotmail.com>
To: airlied@redhat.com, akpm@linux-foundation.org,
christian.koenig@amd.com, daniel@ffwll.ch, david@redhat.com,
dri-devel@lists.freedesktop.org, fengwei.yin@intel.com,
gurchetansingh@chromium.org, hughd@google.com,
kraxel@redhat.com, linaro-mm-sig-bounces@lists.linaro.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-mm@kvack.org,
sumit.semwal@linaro.org, syzkaller-bugs@googlegroups.com,
vivek.kasireddy@intel.com
Subject: Re: [syzbot] [mm?] kernel BUG in filemap_unaccount_folio
Date: Tue, 13 Aug 2024 17:32:03 -0700 [thread overview]
Message-ID: <000000000000ef7be4061f99da2f@google.com> (raw)
In-Reply-To: <000000000000be3c1a0604b53a1c@google.com>
syzbot suspects this issue was fixed by commit:
commit 7d79cd784470395539bda91bf0b3505ff5b2ab6d
Author: Vivek Kasireddy <vivek.kasireddy@intel.com>
Date: Mon Jun 24 06:36:13 2024 +0000
udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17dad691980000
start commit: 9b6de136b5f0 Merge tag 'loongarch-fixes-6.7-1' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6ae1a4ee971a7305
dashboard link: https://syzkaller.appspot.com/bug?extid=17a207d226b8a5fb0fd9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15f58d67680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a78c62e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: udmabuf: use vmf_insert_pfn and VM_PFNMAP for handling mmap
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-08-14 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 18:51 syzbot
2023-09-08 0:50 ` Yin, Fengwei
2023-09-10 7:02 ` Kasireddy, Vivek
2023-09-10 11:53 ` Yin, Fengwei
2024-08-14 0:32 ` 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=000000000000ef7be4061f99da2f@google.com \
--to=syzbot+17a207d226b8a5fb0fd9@syzkaller.appspotmail.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fengwei.yin@intel.com \
--cc=gurchetansingh@chromium.org \
--cc=hughd@google.com \
--cc=kraxel@redhat.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=linux-mm@kvack.org \
--cc=sumit.semwal@linaro.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vivek.kasireddy@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