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: Sun, 09 Sep 2018 06:16:02 -0700 [thread overview]
Message-ID: <000000000000debf740575700af9@google.com> (raw)
In-Reply-To: <0000000000000956640571197f98@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=14800f0a400000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f59875069d721b6
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=16a79cbe400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=172a3d01400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+903cdd6bce9a6eb832a4@syzkaller.appspotmail.com
00000000d154fefb: 000000000044a069 (0x44a069)
000000006f318b9e: 0000000000000033 (0x33)
000000007d449f84: 0000000000000246 (0x246)
00000000e7603b48: 00007f129ff8fce8 (0x7f129ff8fce8)
00000000187b73f3: 000000000000002b (0x2b)
WARNING: kernel stack frame pointer at 00000000c37350d4 in
syz-executor951:10824 has bad value 00000000530130ef
prev parent reply other threads:[~2018-09-09 13:16 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
2018-09-09 13:16 ` 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=000000000000debf740575700af9@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.