From: syzbot <syzbot+17a207d226b8a5fb0fd9@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, christian.koenig@amd.com,
daniel@ffwll.ch, dri-devel@lists.freedesktop.org,
fengwei.yin@intel.com, gurchetansingh@chromium.org,
hughd@google.com, kraxel@redhat.com,
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: Fri, 15 Sep 2023 11:18:26 -0700 [thread overview]
Message-ID: <0000000000009e9e1b060569d17c@google.com> (raw)
In-Reply-To: <000000000000be3c1a0604b53a1c@google.com>
syzbot has bisected this issue to:
commit 5c074eeabbd332b11559f7fc1e89d456f94801fb
Author: Gerd Hoffmann <kraxel@redhat.com>
Date: Wed Nov 14 12:20:29 2018 +0000
udmabuf: set read/write flag when exporting
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12b21bbfa80000
start commit: db906f0ca6bb Merge tag 'phy-for-6.6' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11b21bbfa80000
console output: https://syzkaller.appspot.com/x/log.txt?x=16b21bbfa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=3bd57a1ac08277b0
dashboard link: https://syzkaller.appspot.com/bug?extid=17a207d226b8a5fb0fd9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11609f38680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c1fc00680000
Reported-by: syzbot+17a207d226b8a5fb0fd9@syzkaller.appspotmail.com
Fixes: 5c074eeabbd3 ("udmabuf: set read/write flag when exporting")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2023-09-15 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000be3c1a0604b53a1c@google.com>
2023-09-15 18:18 ` syzbot [this message]
2024-08-14 0:32 ` [syzbot] [mm?] kernel BUG in filemap_unaccount_folio 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=0000000000009e9e1b060569d17c@google.com \
--to=syzbot+17a207d226b8a5fb0fd9@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--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@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