no output from test machine (2)

50 views
Skip to first unread message

syzbot

unread,
Dec 9, 2017, 5:34:05 AM12/9/17
to syzkaller-upst...@googlegroups.com
Hello,

syzkaller hit the following crash on
ae64f9bd1d3621b5e60d7363bc20afb46aede215
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
compiler: gcc (GCC) 7.1.1 20170620
.config is attached
Raw console output is attached.
C reproducer is attached
syzkaller reproducer is attached. See https://goo.gl/kgGztJ
for information about syzkaller reproducers
CC: []



---
This bug is generated by a dumb bot. It may contain errors.
See https://goo.gl/tpsmEJ for details.
Direct all questions to syzk...@googlegroups.com.
Please credit me with: Reported-by: syzbot <syzk...@googlegroups.com>

syzbot will keep track of this bug report.
Once a fix for this bug is merged into any tree, 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.
To upstream this report, please reply with:
#syz upstream
config.txt
raw.log
repro.txt
repro.c

Dmitry Vyukov

unread,
Feb 22, 2018, 7:10:43 AM2/22/18
to syzbot, 'Dmitry Vyukov' via syzkaller-upstream-moderation, Dmitry
populate bug CC list for patch testing testing


On Sat, Dec 9, 2017 at 11:34 AM, syzbot
<bot+2e40940976be9f8fce...@syzkaller.appspotmail.com>
wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to syzkaller-upstream-m...@googlegroups.com.
> To post to this group, send email to
> syzkaller-upst...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/syzkaller-upstream-moderation/001a11444d0e0f4eac055fe5d7cd%40google.com.
> For more options, visit https://groups.google.com/d/optout.

syzbot

unread,
Feb 22, 2018, 7:13:14 AM2/22/18
to Dmitry Vyukov, dvy...@google.com, syzkaller-upst...@googlegroups.com
> testing request without a patch

> #syz test:
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

I don't see any patch attached to the request.

> master

syzbot

unread,
Feb 22, 2018, 7:34:01 AM2/22/18
to dvy...@google.com, syzkaller-upst...@googlegroups.com
Hello,

syzbot has tested the proposed patch and the reproducer did not trigger
crash:

Reported-and-tested-by:
syzbot+2e40940976be9f8f...@syzkaller.appspotmail.com

Note: the tag will also help syzbot to understand when the bug is fixed.

Tested on upstream commit
af3e79d29555b97dd096e2f8e36a0f50213808a8 (Tue Feb 20 18:05:02 2018 +0000)
Merge tag 'leds_for-4.16-rc3' of
git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds

compiler: gcc (GCC) 7.1.1 20170620
Patch is attached.
Kernel config is attached.


---
There is no WARRANTY for the result, to the extent permitted by applicable
law.
Except when otherwise stated in writing syzbot provides the result "AS IS"
without warranty of any kind, either expressed or implied, but not limited
to,
the implied warranties of merchantability and fittness for a particular
purpose.
The entire risk as to the quality of the result is with you. Should the
result
prove defective, you assume the cost of all necessary servicing, repair or
correction.
patch.diff
config.txt
Reply all
Reply to author
Forward
0 new messages