From: syzbot <syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com>
To: cgroups@vger.kernel.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mhocko@kernel.org, syzkaller-bugs@googlegroups.com,
vdavydov.dev@gmail.com
Subject: KASAN: null-ptr-deref Read in reclaim_high
Date: Thu, 10 Jan 2019 09:03:04 -0800 [thread overview]
Message-ID: <000000000000491844057f1d8d2f@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: 6cab33afc3dd Add linux-next specific files for 20190110
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=178b287b400000
kernel config: https://syzkaller.appspot.com/x/.config?x=611f89e5b6868db
dashboard link: https://syzkaller.appspot.com/bug?extid=fa11f9da42b46cea3b4a
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14259017400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141630a0c00000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: null-ptr-deref in atomic64_read
include/generated/atomic-instrumented.h:836 [inline]
BUG: KASAN: null-ptr-deref in atomic_long_read
include/generated/atomic-long.h:28 [inline]
BUG: KASAN: null-ptr-deref in page_counter_read
include/linux/page_counter.h:47 [inline]
BUG: KASAN: null-ptr-deref in reclaim_high.constprop.0+0xa6/0x1e0
mm/memcontrol.c:2149
Read of size 8 at addr 0000000000000138 by task syz-executor037/7964
CPU: 1 PID: 7964 Comm: syz-executor037 Not tainted 5.0.0-rc1-next-20190110
#9
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1db/0x2d0 lib/dump_stack.c:113
kasan_report.cold+0x5/0x40 mm/kasan/report.c:321
check_memory_region_inline mm/kasan/generic.c:185 [inline]
check_memory_region+0x123/0x190 mm/kasan/generic.c:191
kasan_check_read+0x11/0x20 mm/kasan/common.c:100
atomic64_read include/generated/atomic-instrumented.h:836 [inline]
atomic_long_read include/generated/atomic-long.h:28 [inline]
page_counter_read include/linux/page_counter.h:47 [inline]
reclaim_high.constprop.0+0xa6/0x1e0 mm/memcontrol.c:2149
mem_cgroup_handle_over_high+0xc1/0x180 mm/memcontrol.c:2178
tracehook_notify_resume include/linux/tracehook.h:190 [inline]
exit_to_usermode_loop+0x299/0x3b0 arch/x86/entry/common.c:166
prepare_exit_to_usermode arch/x86/entry/common.c:197 [inline]
syscall_return_slowpath+0x519/0x5f0 arch/x86/entry/common.c:268
ret_from_fork+0x15/0x50 arch/x86/entry/entry_64.S:344
RIP: 0033:0x44034a
Code: Bad RIP value.
RSP: 002b:00007ffc31cd3040 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000044034a
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 00007ffc31cd3060 R08: 0000000000000001 R09: 0000000002027880
R10: 0000000002027b50 R11: 0000000000000246 R12: 0000000000000001
R13: 000000000000cc59 R14: 0000000000000000 R15: 0000000000000000
==================================================================
---
This bug is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2019-01-10 17:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 17:03 syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-11 13:08 KASAN: null-ptr-deref Read in reclaim_high syzbot
2019-03-11 23:37 ` 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
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=000000000000491844057f1d8d2f@google.com \
--to=syzbot+fa11f9da42b46cea3b4a@syzkaller.appspotmail.com \
--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=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.