From: syzbot <syzbot+347e2331d03d06ab0224@syzkaller.appspotmail.com>
To: a@unstable.cc, akpm@linux-foundation.org, ast@kernel.org,
b.a.t.m.a.n@lists.open-mesh.org, davem@davemloft.net,
dvyukov@google.com, jbacik@fb.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mareklindner@neomailbox.ch,
mingo@kernel.org, netdev@vger.kernel.org, peterz@infradead.org,
songliubraving@fb.com, sw@simonwunderlich.de,
syzkaller-bugs@googlegroups.com, yhs@fb.com
Subject: Re: BUG: Bad rss-counter state (4)
Date: Mon, 18 May 2020 05:28:05 -0700 [thread overview]
Message-ID: <00000000000071203205a5eb4b43@google.com> (raw)
In-Reply-To: <000000000000ada39605a5e71711@google.com>
syzbot has bisected this bug to:
commit 0d8dd67be013727ae57645ecd3ea2c36365d7da8
Author: Song Liu <songliubraving@fb.com>
Date: Wed Dec 6 22:45:14 2017 +0000
perf/headers: Sync new perf_event.h with the tools/include/uapi version
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13240a02100000
start commit: ac935d22 Add linux-next specific files for 20200415
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=10a40a02100000
console output: https://syzkaller.appspot.com/x/log.txt?x=17240a02100000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc498783097e9019
dashboard link: https://syzkaller.appspot.com/bug?extid=347e2331d03d06ab0224
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d18e6e100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=104170d6100000
Reported-by: syzbot+347e2331d03d06ab0224@syzkaller.appspotmail.com
Fixes: 0d8dd67be013 ("perf/headers: Sync new perf_event.h with the tools/include/uapi version")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-05-18 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000ada39605a5e71711@google.com>
2020-05-18 7:38 ` BUG: Bad rss-counter state (4) Dmitry Vyukov
2020-05-18 12:28 ` syzbot [this message]
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=00000000000071203205a5eb4b43@google.com \
--to=syzbot+347e2331d03d06ab0224@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mareklindner@neomailbox.ch \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).