linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandr Nogikh <nogikh@google.com>
To: linux-riscv@lists.infradead.org,
	kasan-dev <kasan-dev@googlegroups.com>,
	palmer@dabbelt.com, alexandre.ghiti@canonical.com
Cc: syzbot <syzbot+330a558d94b58f7601be@syzkaller.appspotmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] riscv/fixes boot error: can't ssh into the instance
Date: Wed, 2 Feb 2022 12:07:59 +0100	[thread overview]
Message-ID: <CANp29Y7WjwXwgxPrNq0XXjXPu+wGFqTreh9gry=O6aE7+cKpLQ@mail.gmail.com> (raw)
In-Reply-To: <00000000000038779505d5d8b372@google.com>

Hello,

syzbot has already not been able to fuzz its RISC-V instance for 97
days now because the compiled kernel cannot boot. I bisected the issue
to the following commit:

commit 54c5639d8f507ebefa814f574cb6f763033a72a5
Author: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Date:   Fri Oct 29 06:59:27 2021 +0200

    riscv: Fix asan-stack clang build

Apparently, the problem appears on GCC-built RISC-V kernels with KASAN
enabled. In the previous message syzbot mentions
"riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU
Binutils for Debian) 2.35.2", but the issue also reproduces finely on
a newer GCC compiler: "riscv64-linux-gnu-gcc (Debian 11.2.0-10)
11.2.0, GNU ld (GNU Binutils for Debian) 2.37".
For convenience, I also duplicate the .config file from the bot's
message: https://syzkaller.appspot.com/x/.config?x=522544a2e0ef2a7d

Can someone with KASAN and RISC-V expertise please take a look?

--
Best Regards,
Aleksandr


On Tue, Jan 18, 2022 at 11:26 AM syzbot
<syzbot+330a558d94b58f7601be@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    f6f7fbb89bf8 riscv: dts: sifive unmatched: Link the tmp451..
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes
> console output: https://syzkaller.appspot.com/x/log.txt?x=1095f85bb00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=522544a2e0ef2a7d
> dashboard link: https://syzkaller.appspot.com/bug?extid=330a558d94b58f7601be
> compiler:       riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> userspace arch: riscv64
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+330a558d94b58f7601be@syzkaller.appspotmail.com
>
>
>
> ---
> 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.
>
> --
> 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 syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/00000000000038779505d5d8b372%40google.com.

  reply	other threads:[~2022-02-02 11:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 10:26 [syzbot] riscv/fixes boot error: can't ssh into the instance syzbot
2022-02-02 11:07 ` Aleksandr Nogikh [this message]
2022-02-02 13:18   ` Alexandre Ghiti
2022-02-15 17:12     ` Dmitry Vyukov
2022-02-16  4:14       ` Alexandre Ghiti
2022-02-16 10:37         ` Aleksandr Nogikh
2022-02-16 11:47           ` Aleksandr Nogikh
2022-02-16 11:56             ` Dmitry Vyukov
2022-02-16 16:09               ` Aleksandr Nogikh
2022-02-16 16:16                 ` Aleksandr Nogikh
2022-02-16 16:58                   ` Alexandre Ghiti
2022-02-17 16:53                     ` Alexandre Ghiti
2022-02-17 17:07                       ` Aleksandr Nogikh
2022-02-18 13:45                         ` Alexandre Ghiti
2022-02-18 20:33                           ` Aleksandr Nogikh
2022-05-12 11:48                           ` Dmitry Vyukov
2022-05-16 12:05                             ` Alexandre Ghiti
2022-05-26  8:11                               ` Atish Patra
2022-05-26  9:02                                 ` Atish Patra
2022-05-27  7:17                                   ` Dmitry Vyukov
2022-05-27  7:33                                   ` Alexandre Ghiti
2022-05-27 13:04                                     ` Dmitry Vyukov
2022-05-27 22:50                                     ` Atish Patra
2022-05-28  8:13                                       ` Alexandre Ghiti

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='CANp29Y7WjwXwgxPrNq0XXjXPu+wGFqTreh9gry=O6aE7+cKpLQ@mail.gmail.com' \
    --to=nogikh@google.com \
    --cc=alexandre.ghiti@canonical.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=syzbot+330a558d94b58f7601be@syzkaller.appspotmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).