From: syzbot <syzbot+347e2331d03d06ab0224@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: BUG: Bad rss-counter state (4)
Date: Mon, 18 May 2020 00:27:16 -0700 [thread overview]
Message-ID: <000000000000ada39605a5e71711@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: ac935d22 Add linux-next specific files for 20200415
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14b66e6e100000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc498783097e9019
dashboard link: https://syzkaller.appspot.com/bug?extid=347e2331d03d06ab0224
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d18e6e100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=104170d6100000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+347e2331d03d06ab0224@syzkaller.appspotmail.com
BUG: Bad rss-counter state mm:00000000a67744c9 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000f49d6d70 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:0000000006212dd2 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000b6ae35d3 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000d44d5c2e type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:0000000023502204 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:000000001a912a5c type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:0000000072bd9e23 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:0000000053ee80f7 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:000000003cc0aff9 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:000000005a4ef043 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000fe0ab895 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000863004ed type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:0000000064449491 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000f6a209ff type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:000000008100dc4b type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000f80eb0e8 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000475e50a5 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000f2f5edcf type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000bf721456 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000d8d29ec3 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:00000000b5dff60e type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:000000001f0fe928 type:MM_ANONPAGES val:1
BUG: Bad rss-counter state mm:000000006fc01973 type:MM_ANONPAGES val:1
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2020-05-18 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 7:27 syzbot [this message]
2020-05-18 7:38 ` BUG: Bad rss-counter state (4) Dmitry Vyukov
2020-05-18 12:28 ` syzbot
2021-04-11 21:38 ` Vegard Nossum
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=000000000000ada39605a5e71711@google.com \
--to=syzbot+347e2331d03d06ab0224@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--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