From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+94522064b07f06df116d@syzkaller.appspotmail.com>,
David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: linux-next boot error: can't ssh into the instance (2)
Date: Mon, 4 Feb 2019 09:20:16 +0100 [thread overview]
Message-ID: <CACT4Y+Y=-aFQXjqRviYg8Z0eve+_qb1fRkdezeBpio0NkZiK=A@mail.gmail.com> (raw)
In-Reply-To: <000000000000dc52b305810d0f49@google.com>
On Mon, Feb 4, 2019 at 9:13 AM syzbot
<syzbot+94522064b07f06df116d@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 66d54fa79f95 Add linux-next specific files for 20190204
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=17823b28c00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f0f6544db42451b4
> dashboard link: https://syzkaller.appspot.com/bug?extid=94522064b07f06df116d
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> Unfortunately, I don't have any reproducer for this crash yet.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+94522064b07f06df116d@syzkaller.appspotmail.com
[ 6.272518][ T1] BUG: KASAN: global-out-of-bounds in
fs_validate_description+0x109/0x6e9
Probably introduced by:
commit 82685adaccb3e756d04161ebfc9d188b57def10c
Author: David Howells
Date: Thu Nov 1 23:07:24 2018 +0000
vfs: Add configuration parser helpers
> ---
> This bug 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 bug report. See:
> https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
> syzbot.
parent reply other threads:[~2019-02-04 8:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000dc52b305810d0f49@google.com>]
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='CACT4Y+Y=-aFQXjqRviYg8Z0eve+_qb1fRkdezeBpio0NkZiK=A@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+94522064b07f06df116d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).