From: syzbot <syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, cgroups@vger.kernel.org,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@kernel.org, mhocko@suse.com,
sfr@canb.auug.org.au, shakeelb@google.com,
syzkaller-bugs@googlegroups.com, vdavydov.dev@gmail.com
Subject: KASAN: null-ptr-deref Read in reclaim_high
Date: Mon, 11 Mar 2019 06:08:01 -0700 [thread overview]
Message-ID: <0000000000001fd5780583d1433f@google.com> (raw)
syzbot has bisected this bug to:
commit 29a4b8e275d1f10c51c7891362877ef6cffae9e7
Author: Shakeel Butt <shakeelb@google.com>
Date: Wed Jan 9 22:02:21 2019 +0000
memcg: schedule high reclaim for remote memcgs on high_work
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155bf5db200000
start commit: 29a4b8e2 memcg: schedule high reclaim for remote memcgs on..
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=175bf5db200000
console output: https://syzkaller.appspot.com/x/log.txt?x=135bf5db200000
kernel config: https://syzkaller.appspot.com/x/.config?x=611f89e5b6868db
dashboard link: https://syzkaller.appspot.com/bug?extid=fa11f9da42b46cea3b4a
userspace arch: amd64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14259017400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141630a0c00000
Reported-by: syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com
Fixes: 29a4b8e2 ("memcg: schedule high reclaim for remote memcgs on
high_work")
next reply other threads:[~2019-03-11 13:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 13:08 syzbot [this message]
2019-03-11 23:37 ` KASAN: null-ptr-deref Read in reclaim_high Andrew Morton
2019-03-12 6:08 ` Dmitry Vyukov
2019-03-12 6:25 ` Andrew Morton
2019-03-12 6:43 ` Eric Biggers
2019-03-12 8:21 ` Dmitry Vyukov
2019-03-12 22:31 ` Eric Biggers
2019-03-13 8:12 ` Dmitry Vyukov
2019-03-12 8:33 ` Dmitry Vyukov
2019-03-12 13:45 ` Shakeel Butt
2019-03-12 14:44 ` Dmitry Vyukov
2019-03-12 22:50 ` Eric Biggers
2019-03-13 8:24 ` Dmitry Vyukov
2019-03-13 18:16 ` Eric Biggers
2019-03-19 13:52 ` Dmitry Vyukov
-- strict thread matches above, loose matches on Subject: below --
2019-01-10 17:03 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=0000000000001fd5780583d1433f@google.com \
--to=syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=sfr@canb.auug.org.au \
--cc=shakeelb@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vdavydov.dev@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.