LKML Archive on
help / color / mirror / Atom feed
From: Dmitry Vyukov <>
To: syzbot <>
Cc: LKML <>,
	syzkaller-bugs <>,
	Herbert Xu <>,
	David Miller <>,, Eric Biggers <>
Subject: Re: WARNING: kernel stack regs at (ptrval) in syzkaller has bad 'bp' value (ptrval)
Date: Mon, 23 Apr 2018 12:59:30 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Apr 23, 2018 at 12:10 PM, syzbot
<> wrote:
> Hello,
> syzbot hit the following crash on upstream commit
> 5ec83b22a2dd13180762c89698e4e2c2881a423c (Sun Apr 22 19:13:04 2018 +0000)
> Merge tag '4.17-rc1-SMB3-CIFS' of git://
> syzbot dashboard link:
> C reproducer:
> syzkaller reproducer:
> Raw console output:
> Kernel config:
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)

There are 2 similar bugs reported:

They all seem to point to crypto/SHA3/K512_4.
+crypto maintainers

> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by:
> It will help syzbot understand when the bug is fixed. See footer for
> details.
> If you forward the report, please keep this part and the footer.
>         (ptrval): 0000000000445649 (0x445649)
>         (ptrval): 0000000000000033 (0x33)
>         (ptrval): 0000000000000216 (0x216)
>         (ptrval): 00007f155536eda8 (0x7f155536eda8)
>         (ptrval): 000000000000002b (0x2b)
> WARNING: kernel stack regs at         (ptrval) in syzkaller547737:4493 has
> bad 'bp' value         (ptrval)
> WARNING: kernel stack frame pointer at         (ptrval) in
> syzkaller547737:4496 has bad value         (ptrval)
> ---
> This bug is generated by a dumb bot. It may contain errors.
> See for details.
> Direct all questions to
> syzbot will keep track of this bug report.
> If you forgot to add the Reported-by tag, once the fix for this bug is
> merged
> into any tree, please reply to this email with:
> #syz fix: exact-commit-title
> If you want to test a patch for this bug, please reply with:
> #syz test: git://repo/address.git branch
> and provide the patch inline or as an attachment.
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> If it's a one-off invalid bug report, please reply with:
> #syz invalid
> Note: if the crash happens again, it will cause creation of a new bug
> report.
> Note: all commands must start from beginning of the line in the email body.
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
> To view this discussion on the web visit
> For more options, visit

      reply	other threads:[~2018-04-23 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 10:10 WARNING: kernel stack regs at (ptrval) in syzkaller has bad 'bp' value (ptrval) syzbot
2018-04-23 10:59 ` Dmitry Vyukov [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \

* 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).