All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6e2ccedb96d1174e6a5f@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org,
	dan.carpenter@linaro.org,  linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	llvm@lists.linux.dev, mike.kravetz@oracle.com,
	 muchun.song@linux.dev, nathan@kernel.org,
	ndesaulniers@google.com,  sidhartha.kumar@oracle.com,
	syzkaller-bugs@googlegroups.com, trix@redhat.com,
	 viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] general protection fault in pagemap_scan_hugetlb_entry
Date: Sat, 30 Dec 2023 10:24:08 -0800	[thread overview]
Message-ID: <00000000000025c17f060dbe41ef@google.com> (raw)
In-Reply-To: <000000000000fdfe4b060b91993f@google.com>

syzbot suspects this issue was fixed by commit:

commit 4a3ef6be03e6700037fc20e63aa5ffd972e435ca
Author: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Date:   Mon Dec 4 18:32:34 2023 +0000

    mm/hugetlb: have CONFIG_HUGETLB_PAGE select CONFIG_XARRAY_MULTI

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=126d4145e80000
start commit:   df60cee26a2e Merge tag '6.7-rc3-smb3-server-fixes' of git:..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=bb39fe85d254f638
dashboard link: https://syzkaller.appspot.com/bug?extid=6e2ccedb96d1174e6a5f
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17befd62e80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10d5a90ce80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: mm/hugetlb: have CONFIG_HUGETLB_PAGE select CONFIG_XARRAY_MULTI

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2023-12-30 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-03  2:17 [syzbot] [fs?] general protection fault in pagemap_scan_hugetlb_entry syzbot
2023-12-06 18:58 ` [syzbot] " syzbot
2023-12-06 19:18 ` syzbot
2023-12-30 18:24 ` syzbot [this message]
     [not found] <CH0PR10MB511315588F14A86E6A3E332D9584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:07 ` syzbot
     [not found] <CH0PR10MB51136103C0ACAF2364167F8F9584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:11 ` syzbot
     [not found] <CH0PR10MB5113962CF629630251AD43D69584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:13 ` syzbot
     [not found] <CH0PR10MB51135FB61C11679C71E9151B9584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:16 ` syzbot
     [not found] <CH0PR10MB51134D414F3002960A5BCEB99584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 19:41 ` syzbot
     [not found] <CH0PR10MB5113DA035381743379D344F99584A@CH0PR10MB5113.namprd10.prod.outlook.com>
2023-12-06 20:36 ` 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=00000000000025c17f060dbe41ef@google.com \
    --to=syzbot+6e2ccedb96d1174e6a5f@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=mike.kravetz@oracle.com \
    --cc=muchun.song@linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=sidhartha.kumar@oracle.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=trix@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.