From: syzbot <syzbot+903cdd6bce9a6eb832a4@syzkaller.appspotmail.com>
To: ak@linux.intel.com, dvyukov@google.com, ebiggers@google.com,
hpa@zytor.com, jgross@suse.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, luto@kernel.org,
megha.dey@linux.intel.com, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: WARNING: kernel stack frame pointer has bad value (2)
Date: Mon, 27 Aug 2018 10:58:02 -0700 [thread overview]
Message-ID: <00000000000074e86d05746e77cc@google.com> (raw)
In-Reply-To: <0000000000000956640571197f98@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 2ad0d5269970 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14f7f36a400000
kernel config: https://syzkaller.appspot.com/x/.config?x=79e695838ce7a210
dashboard link: https://syzkaller.appspot.com/bug?extid=903cdd6bce9a6eb832a4
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c5a07a400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+903cdd6bce9a6eb832a4@syzkaller.appspotmail.com
0000000077534c7d: ffff8801d3be2188 (0xffff8801d3be2188)
00000000d99670e0: ffff8801cf5dbdf0 (0xffff8801cf5dbdf0)
0000000092c01301: ffff8801cf5dbd10 (0xffff8801cf5dbd10)
0000000039ac4013: ffffffff86c00d4a (do_softirq_own_stack+0x2a/0x40)
00000000f205f6c7: ffff8801cf5dbd10 (0xffff8801cf5dbd10)
WARNING: kernel stack frame pointer at 0000000092c01301 in
syz-executor0:4993 has bad value 0000000097e4bf07
==================================================================
BUG: KASAN: stack-out-of-bounds in schedule_debug kernel/sched/core.c:3283
[inline]
BUG: KASAN: stack-out-of-bounds in __schedule+0x1a18/0x1ec0
kernel/sched/core.c:3393
Read of size 8 at addr ffff8801cf630000 by task syz-executor0/4993
CPU: 1 PID: 4993 Comm: syz-executor0 Not tainted 4.18.0+ #190
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
The buggy address belongs to the page:
page:ffffea00073d8c00 count:1 mapcount:-512 mapping:0000000000000000
index:0x0
flags: 0x2fffc0000000000()
raw: 02fffc0000000000 dead000000000100 dead000000000200 0000000000000000
raw: 0000000000000000 0000000000000000 00000001fffffdff ffff8801aee52b80
page dumped because: kasan: bad access detected
page->mem_cgroup:ffff8801aee52b80
Memory state around the buggy address:
ffff8801cf62ff00: f2 f2 f2 f2 f2 f2 00 f2 f2 f2 00 00 00 00 00 00
ffff8801cf62ff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> ffff8801cf630000: f1 f1 f1 f1 00 f2 f2 f2 f2 f2 f2 f2 04 f2 f2 f2
^
ffff8801cf630080: f2 f2 f2 f2 00 f2 f2 f2 00 00 00 00 00 00 00 00
ffff8801cf630100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1
==================================================================
next prev parent reply other threads:[~2018-08-27 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 8:20 WARNING: kernel stack frame pointer has bad value (2) syzbot
2018-07-16 8:29 ` Dmitry Vyukov
2018-08-27 17:58 ` syzbot [this message]
2018-09-09 13:16 ` 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=00000000000074e86d05746e77cc@google.com \
--to=syzbot+903cdd6bce9a6eb832a4@syzkaller.appspotmail.com \
--cc=ak@linux.intel.com \
--cc=dvyukov@google.com \
--cc=ebiggers@google.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=megha.dey@linux.intel.com \
--cc=mingo@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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.