From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+f2a1633f249cece865fe@syzkaller.appspotmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>, Linux-MM <linux-mm@kvack.org>
Subject: Re: BUG: Bad rss-counter state (3)
Date: Thu, 19 Apr 2018 09:58:40 +0200 [thread overview]
Message-ID: <CACT4Y+ZU9Cznk6jPQ19LPUVch446EUbuj-_yW2ZoSt=6Z2B4YQ@mail.gmail.com> (raw)
In-Reply-To: <000000000000f6e29f056a2edff8@google.com>
On Thu, Apr 19, 2018 at 9:54 AM, syzbot
<syzbot+f2a1633f249cece865fe@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
> a27fc14219f2e3c4a46ba9177b04d9b52c875532 (Mon Apr 16 21:07:39 2018 +0000)
> Merge branch 'parisc-4.17-3' of
> git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux
> syzbot dashboard link:
> https://syzkaller.appspot.com/bug?extid=f2a1633f249cece865fe
>
> So far this crash happened 8 times on upstream.
> C reproducer: https://syzkaller.appspot.com/x/repro.c?id=6258099799195648
> syzkaller reproducer:
> https://syzkaller.appspot.com/x/repro.syz?id=5162423375888384
> Raw console output:
> https://syzkaller.appspot.com/x/log.txt?id=4959118615904256
> Kernel config:
> https://syzkaller.appspot.com/x/.config?id=-5914490758943236750
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+f2a1633f249cece865fe@syzkaller.appspotmail.com
> It will help syzbot understand when the bug is fixed. See footer for
> details.
> If you forward the report, please keep this part and the footer.
+mm maintainers (syzbot wasn't able to find maintainers because there
is no stack trace and no file names to give to get_maintainers.pl)
There is a single-threaded reproducer, so should be an easy one.
> BUG: Bad rss-counter state mm:00000000d5737ed7 idx:1 val:1
> BUG: Bad rss-counter state mm:00000000d5737ed7 idx:3 val:-1
>
>
> ---
> This bug is generated by a dumb bot. It may contain errors.
> See https://goo.gl/tpsmEJ for details.
> Direct all questions to syzkaller@googlegroups.com.
>
> syzbot will keep track of this bug report.
> If you forgot to add the Reported-by tag, once the fix for this bug is
> merged
> into any tree, please reply to this email with:
> #syz fix: exact-commit-title
> If you want to test a patch for this bug, please reply with:
> #syz test: git://repo/address.git branch
> and provide the patch inline or as an attachment.
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> If it's a one-off invalid bug report, please reply with:
> #syz invalid
> Note: if the crash happens again, it will cause creation of a new bug
> report.
> Note: all commands must start from beginning of the line in the email body.
>
> --
> 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/000000000000f6e29f056a2edff8%40google.com.
> For more options, visit https://groups.google.com/d/optout.
next parent reply other threads:[~2018-04-19 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000f6e29f056a2edff8@google.com>
2018-04-19 7:58 ` Dmitry Vyukov [this message]
2019-12-09 1:38 ` 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='CACT4Y+ZU9Cznk6jPQ19LPUVch446EUbuj-_yW2ZoSt=6Z2B4YQ@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=syzbot+f2a1633f249cece865fe@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