From: syzbot <syzbot+5493b2a54d31d6aea629@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, davem@davemloft.net, guro@fb.com,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
lizefan@huawei.com, lizf@cn.fujitsu.com, menage@google.com,
mingo@redhat.com, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: Re: WARNING in cgroup_apply_control_enable
Date: Sat, 23 Nov 2019 07:29:00 -0800 [thread overview]
Message-ID: <0000000000008fdf12059805304e@google.com> (raw)
In-Reply-To: <00000000000009f9a305708faf46@google.com>
syzbot has bisected this bug to:
commit 0d5936344f30aba0f6ddb92b030cb6a05168efe6
Author: Tejun Heo <tj@kernel.org>
Date: Mon Sep 25 16:00:19 2017 +0000
sched: Implement interface for cgroup unified hierarchy
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16142bd2e00000
start commit: 3a272031 Merge tag 'libnvdimm-fixes-4.19-rc8' of git://git..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=15142bd2e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=11142bd2e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=88e9a8a39dc0be2d
dashboard link: https://syzkaller.appspot.com/bug?extid=5493b2a54d31d6aea629
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11c890f6400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a94dd6400000
Reported-by: syzbot+5493b2a54d31d6aea629@syzkaller.appspotmail.com
Fixes: 0d5936344f30 ("sched: Implement interface for cgroup unified
hierarchy")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-11-23 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 11:55 WARNING in cgroup_apply_control_enable syzbot
2018-10-14 0:11 ` syzbot
2019-11-23 15:29 ` 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=0000000000008fdf12059805304e@google.com \
--to=syzbot+5493b2a54d31d6aea629@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).