From: syzbot <syzbot+ec78016e3d67860eec28@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org, hdanton@sina.com,
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, riel@surriel.com,
syzkaller-bugs@googlegroups.com, trix@redhat.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [mm?] WARNING in copy_hugetlb_page_range
Date: Tue, 03 Oct 2023 22:16:33 -0700 [thread overview]
Message-ID: <0000000000005d185b0606dd1cbf@google.com> (raw)
In-Reply-To: <0000000000005f05820606a0838a@google.com>
syzbot has bisected this issue to:
commit 446503572dc452fc544d6898113feb0f3801477b
Author: Rik van Riel <riel@surriel.com>
Date: Sun Oct 1 00:55:50 2023 +0000
hugetlbfs: replace hugetlb_vma_lock with invalidate_lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=146c879e680000
start commit: c9f2baaa18b5 Add linux-next specific files for 20231003
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=166c879e680000
console output: https://syzkaller.appspot.com/x/log.txt?x=126c879e680000
kernel config: https://syzkaller.appspot.com/x/.config?x=3fe9c462fee1649f
dashboard link: https://syzkaller.appspot.com/bug?extid=ec78016e3d67860eec28
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e4b011680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11772062680000
Reported-by: syzbot+ec78016e3d67860eec28@syzkaller.appspotmail.com
Fixes: 446503572dc4 ("hugetlbfs: replace hugetlb_vma_lock with invalidate_lock")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-10-04 5:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 4:58 [syzbot] [mm?] WARNING in copy_hugetlb_page_range syzbot
2023-10-03 17:23 ` syzbot
2023-10-03 17:29 ` Mike Kravetz
2023-10-04 3:26 ` Rik van Riel
2023-10-04 5:16 ` syzbot [this message]
[not found] <20231004004602.1789-1-hdanton@sina.com>
2023-10-04 1:20 ` syzbot
[not found] <20231004090157.1850-1-hdanton@sina.com>
2023-10-04 9:27 ` 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=0000000000005d185b0606dd1cbf@google.com \
--to=syzbot+ec78016e3d67860eec28@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=hdanton@sina.com \
--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=riel@surriel.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.