From: Andrew Morton <akpm@linux-foundation.org>
To: syzbot <syzbot+d7ed29a6231d3747fb31@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel BUG in hugepage_add_anon_rmap
Date: Tue, 1 Mar 2022 09:33:48 -0800 [thread overview]
Message-ID: <20220301093348.0eb7071cab3d8f0e49613fdf@linux-foundation.org> (raw)
In-Reply-To: <0000000000009ee0ca05d9288b83@google.com>
On Tue, 01 Mar 2022 05:57:27 -0800 syzbot <syzbot+d7ed29a6231d3747fb31@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 196d330d7fb1 Add linux-next specific files for 20220222
This seems to be a relatively old kernel?
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=15b0618a700000
> kernel config: https://syzkaller.appspot.com/x/.config?x=45b71d0aea81d553
> dashboard link: https://syzkaller.appspot.com/bug?extid=d7ed29a6231d3747fb31
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+d7ed29a6231d3747fb31@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at mm/rmap.c:2330!
BUG_ON(!PageLocked(page)) in hugepage_add_anon_rmap()
next prev parent reply other threads:[~2022-03-01 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 13:57 syzbot
2022-03-01 17:30 ` Hugh Dickins
2022-03-02 13:50 ` Dmitry Vyukov
2022-03-01 17:33 ` Andrew Morton [this message]
2022-03-01 17:41 ` Aleksandr Nogikh
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=20220301093348.0eb7071cab3d8f0e49613fdf@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+d7ed29a6231d3747fb31@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox