From: Aleksandr Nogikh <nogikh@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+d7ed29a6231d3747fb31@syzkaller.appspotmail.com>,
LKML <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 18:41:17 +0100 [thread overview]
Message-ID: <CANp29Y77+GDjoc0H_tr9DzDYTCSaqq14R2Ghy=bF7Ens+366Jg@mail.gmail.com> (raw)
In-Reply-To: <20220301093348.0eb7071cab3d8f0e49613fdf@linux-foundation.org>
On Tue, Mar 1, 2022 at 6:33 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> 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?
Yes, syzbot was unfortunately unable to switch to the newer linux-next
versions for several days because they triggered the "WARNING in
__mod_memcg_lruvec_state" error during boot.
https://syzkaller.appspot.com/bug?id=f7421a1372deecbdb46bd6fb35ce84b16024b7f5
Now the problem is gone and syzbot is running the latest 20220301 version.
>
> > 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()
>
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/20220301093348.0eb7071cab3d8f0e49613fdf%40linux-foundation.org.
prev parent reply other threads:[~2022-03-01 17:41 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
2022-03-01 17:41 ` Aleksandr Nogikh [this message]
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='CANp29Y77+GDjoc0H_tr9DzDYTCSaqq14R2Ghy=bF7Ens+366Jg@mail.gmail.com' \
--to=nogikh@google.com \
--cc=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