Messages in this thread | | | Date | Mon, 23 Apr 2018 03:10:01 -0700 | Subject | WARNING: kernel stack frame pointer at (ptrval) in syzkaller has bad value (ptrval) | From | syzbot <> |
| |
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://git.samba.org/sfrench/cifs-2.6 syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=e81cee75d9f3fe72ec33
C reproducer: https://syzkaller.appspot.com/x/repro.c?id=4545675937185792 syzkaller reproducer: https://syzkaller.appspot.com/x/repro.syz?id=6597511200374784 Raw console output: https://syzkaller.appspot.com/x/log.txt?id=4986591978192896 Kernel config: https://syzkaller.appspot.com/x/.config?id=1808800213120130118 compiler: gcc (GCC) 8.0.1 20180413 (experimental)
IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+e81cee75d9f3fe72ec33@syzkaller.appspotmail.com 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): 000000000043fe19 (0x43fe19) (ptrval): 0000000000000033 (0x33) (ptrval): 0000000000000216 (0x216) (ptrval): 00007ffd01ce4bd8 (0x7ffd01ce4bd8) (ptrval): 000000000000002b (0x2b) WARNING: kernel stack frame pointer at (ptrval) in syzkaller601944:4492 has bad value (ptrval) WARNING: kernel stack regs at (ptrval) in syzkaller601944:4492 has bad 'bp' value (ptrval)
--- This bug is generated by a dumb bot. It may contain errors. See https://goo.gl/tpsmEJ for details. Direct all questions to syzkaller@googlegroups.com.
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.
| |