From: syzbot <syzbot+9ce030d4c89856b27619@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] unexpected kernel reboot (4)
Date: Tue, 13 Apr 2021 14:27:13 -0700 [thread overview]
Message-ID: <000000000000301a4d05bfe14b8f@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 89698bec Merge tag 'm68knommu-for-v5.12-rc7' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1243fcfed00000
kernel config: https://syzkaller.appspot.com/x/.config?x=b234ddbbe2953747
dashboard link: https://syzkaller.appspot.com/bug?extid=9ce030d4c89856b27619
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=173e92fed00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1735da2ed00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9ce030d4c89856b27619@syzkaller.appspotmail.com
output_len: 0x000000000e74eb68
kernel_total_size: 0x000000000f226000
needed_size: 0x000000000f400000
trampoline_32bit: 0x000000000009d000
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2021-04-13 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 21:27 syzbot [this message]
2021-04-14 5:45 ` [syzbot] unexpected kernel reboot (4) Dmitry Vyukov
2021-04-14 15:39 ` Andrey Konovalov
2021-04-14 16:16 ` Tetsuo Handa
2021-04-22 10:16 ` Tetsuo Handa
2021-04-22 14:20 ` Dmitry Vyukov
2021-04-22 16:13 ` Tetsuo Handa
2021-04-22 17:00 ` Dmitry Vyukov
2021-04-17 3:19 ` Tetsuo Handa
2021-04-18 15:09 ` Tetsuo Handa
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=000000000000301a4d05bfe14b8f@google.com \
--to=syzbot+9ce030d4c89856b27619@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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