From: syzbot <syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com>
To: airlied@redhat.com, akpm@linux-foundation.org, david@redhat.com,
dri-devel@lists.freedesktop.org, kraxel@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
muchun.song@linux.dev, steven.sistare@oracle.com,
syzkaller-bugs@googlegroups.com, vivek.kasireddy@intel.com
Subject: Re: [syzbot] [mm?] kernel BUG in alloc_hugetlb_folio_reserve
Date: Sun, 02 Feb 2025 09:27:04 -0800 [thread overview]
Message-ID: <679faae8.050a0220.d7c5a.0073.GAE@google.com> (raw)
In-Reply-To: <677928b5.050a0220.3b53b0.004d.GAE@google.com>
syzbot has bisected this issue to:
commit c6a3194c05e7e6fd0e8fbfb1720084ae2503c4ac
Author: Vivek Kasireddy <vivek.kasireddy@intel.com>
Date: Mon Jun 24 06:36:16 2024 +0000
udmabuf: pin the pages using memfd_pin_folios() API
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12c71724580000
start commit: 69e858e0b8b2 Merge tag 'uml-for-linus-6.14-rc1' of git://g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=11c71724580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16c71724580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d033b14aeef39158
dashboard link: https://syzkaller.appspot.com/bug?extid=a504cb5bae4fe117ba94
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1324fddf980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128b55f8580000
Reported-by: syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com
Fixes: c6a3194c05e7 ("udmabuf: pin the pages using memfd_pin_folios() API")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-02-02 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 12:25 syzbot
2025-01-06 3:36 ` Muchun Song
2025-01-07 1:07 ` Kasireddy, Vivek
2025-01-07 1:07 ` syzbot
2025-02-01 20:51 ` syzbot
2025-02-02 4:51 ` Kasireddy, Vivek
2025-02-02 8:42 ` syzbot
2025-02-03 18:51 ` Kasireddy, Vivek
2025-02-03 19:25 ` syzbot
2025-02-02 17:27 ` 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=679faae8.050a0220.d7c5a.0073.GAE@google.com \
--to=syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=steven.sistare@oracle.com \
--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