From: syzbot <syzbot+f2a1633f249cece865fe@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, dvyukov@google.com, hughd@google.com,
jglisse@redhat.com, khlebnikov@yandex-team.ru,
kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@suse.com,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
willy@infradead.org
Subject: Re: BUG: Bad rss-counter state (3)
Date: Sun, 08 Dec 2019 17:38:00 -0800 [thread overview]
Message-ID: <000000000000217e8d05993b7298@google.com> (raw)
In-Reply-To: <000000000000f6e29f056a2edff8@google.com>
syzbot suspects this bug was fixed by commit:
commit 173d9d9fd3ddae84c110fea8aedf1f26af6be9ec
Author: Hugh Dickins <hughd@google.com>
Date: Fri Nov 30 22:10:16 2018 +0000
mm/huge_memory: splitting set mapping+index before unfreeze
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14202b7ae00000
start commit: a27fc142 Merge branch 'parisc-4.17-3' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=adeb81fdb5db9d72
dashboard link: https://syzkaller.appspot.com/bug?extid=f2a1633f249cece865fe
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1257325b800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163bb567800000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: mm/huge_memory: splitting set mapping+index before unfreeze
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-09 1:38 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
2019-12-09 1:38 ` syzbot [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=000000000000217e8d05993b7298@google.com \
--to=syzbot+f2a1633f249cece865fe@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=hughd@google.com \
--cc=jglisse@redhat.com \
--cc=khlebnikov@yandex-team.ru \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
/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