From: syzbot <syzbot+6e2ccedb96d1174e6a5f@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, sidhartha.kumar@oracle.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] general protection fault in pagemap_scan_hugetlb_entry
Date: Wed, 06 Dec 2023 11:07:06 -0800 [thread overview]
Message-ID: <000000000000a0232e060bdc0e9e@google.com> (raw)
In-Reply-To: <CH0PR10MB511315588F14A86E6A3E332D9584A@CH0PR10MB5113.namprd10.prod.outlook.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
mm/hugetlb.c:6485:17: error: too few arguments to function 'set_huge_pte_at'
Tested on:
commit: bee0e776 Merge tag 'for-linus-iommufd' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=bb39fe85d254f638
dashboard link: https://syzkaller.appspot.com/bug?extid=6e2ccedb96d1174e6a5f
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1621e60ee80000
next parent reply other threads:[~2023-12-06 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CH0PR10MB511315588F14A86E6A3E332D9584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:07 ` syzbot [this message]
[not found] <CH0PR10MB5113DA035381743379D344F99584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 20:36 ` [syzbot] [fs?] general protection fault in pagemap_scan_hugetlb_entry syzbot
[not found] <CH0PR10MB51134D414F3002960A5BCEB99584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:41 ` syzbot
[not found] <CH0PR10MB51135FB61C11679C71E9151B9584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:16 ` syzbot
[not found] <CH0PR10MB5113962CF629630251AD43D69584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:13 ` syzbot
[not found] <CH0PR10MB51136103C0ACAF2364167F8F9584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:11 ` syzbot
2023-12-03 2:17 syzbot
2023-12-30 18:24 ` 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=000000000000a0232e060bdc0e9e@google.com \
--to=syzbot+6e2ccedb96d1174e6a5f@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sidhartha.kumar@oracle.com \
--cc=syzkaller-bugs@googlegroups.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.