From: syzbot <syzbot+dcf3f48f4bfe47a2f80a@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, mike.kravetz@oracle.com,
muchun.song@linux.dev, riel@surriel.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [mm?] WARNING in page_vma_mapped_walk
Date: Wed, 04 Oct 2023 15:00:33 -0700 [thread overview]
Message-ID: <000000000000eb6d0b0606eb2201@google.com> (raw)
In-Reply-To: <0000000000001dd5e20606a0d265@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=12c93c16680000
start commit: c9f2baaa18b5 Add linux-next specific files for 20231003
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11c93c16680000
console output: https://syzkaller.appspot.com/x/log.txt?x=16c93c16680000
kernel config: https://syzkaller.appspot.com/x/.config?x=3fe9c462fee1649f
dashboard link: https://syzkaller.appspot.com/bug?extid=dcf3f48f4bfe47a2f80a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1421389a680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12860a7c680000
Reported-by: syzbot+dcf3f48f4bfe47a2f80a@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 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 5:20 [syzbot] [mm?] WARNING in page_vma_mapped_walk syzbot
2023-10-04 4:37 ` syzbot
2023-10-04 22:00 ` syzbot [this message]
[not found] <20231004105010.1901-1-hdanton@sina.com>
2023-10-04 13:06 ` 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=000000000000eb6d0b0606eb2201@google.com \
--to=syzbot+dcf3f48f4bfe47a2f80a@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=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=riel@surriel.com \
--cc=syzkaller-bugs@googlegroups.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.