From: syzbot <syzbot+569ed13f4054f271087b@syzkaller.appspotmail.com>
To: airlied@redhat.com, akpm@linux-foundation.org, kraxel@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
muchun.song@linux.dev, osalvador@suse.de,
syzkaller-bugs@googlegroups.com, vivek.kasireddy@intel.com
Subject: Re: [syzbot] [mm?] general protection fault in dequeue_hugetlb_folio_nodemask (2)
Date: Wed, 12 Jun 2024 04:58:04 -0700 [thread overview]
Message-ID: <0000000000004acf7b061ab01899@google.com> (raw)
In-Reply-To: <0000000000004f12bb061a9acf07@google.com>
syzbot has bisected this issue to:
commit 265a5cde9462d3a816b18c6cf4f0a231f1c29d1b
Author: Vivek Kasireddy <vivek.kasireddy@intel.com>
Date: Thu Apr 11 06:59:43 2024 +0000
udmabuf: pin the pages using memfd_pin_folios() API
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1617ab6a980000
start commit: d35b2284e966 Add linux-next specific files for 20240607
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1517ab6a980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1117ab6a980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d8bf5cd6bcca7343
dashboard link: https://syzkaller.appspot.com/bug?extid=569ed13f4054f271087b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15eb5e86980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15db597e980000
Reported-by: syzbot+569ed13f4054f271087b@syzkaller.appspotmail.com
Fixes: 265a5cde9462 ("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:[~2024-06-12 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 10:34 [syzbot] [mm?] general protection fault in dequeue_hugetlb_folio_nodemask (2) syzbot
2024-06-11 17:30 ` Andrew Morton
2024-06-11 17:46 ` Oscar Salvador
2024-06-11 17:52 ` Oscar Salvador
2024-06-12 5:11 ` Oscar Salvador
2024-06-12 5:55 ` Kasireddy, Vivek
2024-06-12 7:46 ` Oscar Salvador
2024-06-12 8:16 ` syzbot
2024-06-12 11:58 ` 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=0000000000004acf7b061ab01899@google.com \
--to=syzbot+569ed13f4054f271087b@syzkaller.appspotmail.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--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 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.