From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+e01a53d277c86c4e61e7c84ec83432ed395c7df8@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au, hpa@zytor.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: WARNING: kernel stack regs has bad 'bp' value (2)
Date: Thu, 30 Nov 2017 01:17:24 -0800 [thread overview]
Message-ID: <20171130091724.GC5451@zzz.localdomain> (raw)
In-Reply-To: <001a113f2cd26f3532055f0f4a79@google.com>
On Tue, Nov 28, 2017 at 10:36:01AM -0800, syzbot wrote:
> WARNING: kernel stack regs at ffff8801c1e5f468 in syzkaller196611:6199 has
> bad 'bp' value 0000000000000001
> unwind stack type:0 next_sp: (null) mask:0x6 graph_idx:0
> ffff8801db4075a8: ffff8801db407630 (0xffff8801db407630)
> ffff8801db4075b0: ffffffff8128a84e (__save_stack_trace+0x6e/0xd0)
> ffff8801db4075b8: 0000000000000000 ...
> ffff8801db4075c0: ffff8801c1e58000 (0xffff8801c1e58000)
> ffff8801db4075c8: ffff8801c1e60000 (0xffff8801c1e60000)
> ffff8801db4075d0: 0000000000000000 ...
> ffff8801db4075d8: 0000000000000006 (0x6)
> ffff8801db4075e0: ffff8801c1e4e000 (0xffff8801c1e4e000)
> ffff8801db4075e8: 0000010100000000 (0x10100000000)
> ffff8801db4075f0: 0000000000000000 ...
> ffff8801db4075f8: ffff8801db4075a8 (0xffff8801db4075a8)
> ffff8801db407600: ffffffff8134ff7d (__twofish_enc_blk_3way+0x1b1d/0x1b30)
Looks like the x86_64 "3 way" version of Twofish (twofish-x86_64-asm_64-3way.S)
needs to be updated to not use %rbp.
Eric
next prev parent reply other threads:[~2017-11-30 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 18:36 WARNING: kernel stack regs has bad 'bp' value (2) syzbot
2017-11-30 9:17 ` Eric Biggers [this message]
2017-12-27 18:29 ` Dmitry Vyukov
2017-12-28 7:30 ` Dmitry Vyukov
2017-12-19 0:40 ` [PATCH] crypto: x86/twofish-3way - Fix %rbp usage Eric Biggers
2017-12-19 7:54 ` Ingo Molnar
2017-12-19 8:04 ` Juergen Gross
2017-12-19 14:37 ` David Laight
2017-12-19 17:35 ` Ingo Molnar
2017-12-19 22:37 ` Josh Poimboeuf
2017-12-28 7:02 ` Herbert Xu
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=20171130091724.GC5451@zzz.localdomain \
--to=ebiggers3@gmail.com \
--cc=bot+e01a53d277c86c4e61e7c84ec83432ed395c7df8@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).