Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp1646621pxb; Wed, 2 Feb 2022 09:20:37 -0800 (PST) X-Google-Smtp-Source: ABdhPJz3I4Hd7L3LkSyCe+BsFt9Sqkpbmkx7bCvtrkvH529ukw1jYtlHsvK26QdmOiKLAsoNvOi5 X-Received: by 2002:a05:6a00:1305:: with SMTP id j5mr30507462pfu.34.1643822437435; Wed, 02 Feb 2022 09:20:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643822437; cv=none; d=google.com; s=arc-20160816; b=GAEriDbJpkShoQGeQvSXuckXsDu+s+DvHgyoBzS8UdW1i/7shwFwG/HKa7/XaSoEQQ ykT1ZRp4DKNFIJh8viW+Kv4NyvNrPCSb2xntY7G2bpeACYp2CjRkSSQKLmFhNRaJCv0l czq/nBTu27E+b5qYSXuedxuTiXWpiNzU7PGYU/XJfSaqu4hAe/ve63KE1BIew4Ah4xtb /go6/I4hcLySSVEKDcfx5jPv/5zx9if+9NwouygUawY0Tiu2zgM2DRW4gb0zQCwDwZR1 L8nefUFy1Xgv7QV9a3lGYLVmqLgac/NjCFpZnpriYArUBaijkDwm+R/2O2KvqytRAaBu GwJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=snnqrCI4qkz8Hro6Gqsu3aM3hUykyWW5o1MMGnMsu4c=; b=yr7YazhwlCWv8HgVGEksWDA2KU+awaSLA0EE1iyY4bBZiYvUKE/mRhyEz7zgpb8Spy PqRb7cA0iTE6Q0nyndIBgxpipFFrHxO2oqq4NV+K8t22nIdG6amOVMYR3kFtvSNUEmhj WwvclLoxsxGBd9JhhoFMlUksZBN58RElsSRkh4vgTvO7ZHwXtaN+9KaEyDO491jmYY// GSJSt1uZ7nZG57syrZf2kBySAVTf9k5PoZclXrmW4dGqn1toZSnlGaJsvBoWCfwZE9an wgihtbfh/u3f+8ppXXR+Ote5xnJFZk2uNx4n16r1GlJu4vBB5oRuoRIOP+Ivyu8b5LQt 7Olg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canonical.com header.s=20210705 header.b=BMuX1U50; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t19si20843207pgu.571.2022.02.02.09.20.24; Wed, 02 Feb 2022 09:20:37 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@canonical.com header.s=20210705 header.b=BMuX1U50; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344295AbiBBNSv (ORCPT + 99 others); Wed, 2 Feb 2022 08:18:51 -0500 Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]:41580 "EHLO smtp-relay-internal-1.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233464AbiBBNSu (ORCPT ); Wed, 2 Feb 2022 08:18:50 -0500 Received: from mail-ej1-f71.google.com (mail-ej1-f71.google.com [209.85.218.71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id 57C593F1F0 for ; Wed, 2 Feb 2022 13:18:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1643807929; bh=snnqrCI4qkz8Hro6Gqsu3aM3hUykyWW5o1MMGnMsu4c=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=BMuX1U50NYei+gExcEJCwUPseP/qvVfvdviixjVLhklBL9h1ksUyYHk2qJ4D9yGGr o3T3bpjSS7nUJFgbFS6wuUfO5Be914irJivSc8Bpyfi3crLJHUhC7QN6g+RN7knLkg ex0onBLxNzSdy9tYGUpEyjA84u0/FyVgZAlPqnYqb5Emf5FNRXL7kZwKzI9yf3iaHH CG0VODGcJh7ACIiJSwkygsi2dvaonv8PcDD3HQYdgyXrxlFPKY26LPRTPCXWvJpYbE wWIEY1YHR6YTtWKz1Cm/ZRKMAM6jxLZrIn4cMODmyGqcew2xWqlMWA5izJmxHf0qKd G9GpjXiikPRGA== Received: by mail-ej1-f71.google.com with SMTP id i21-20020a1709063c5500b006b4c7308c19so8107967ejg.14 for ; Wed, 02 Feb 2022 05:18:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=snnqrCI4qkz8Hro6Gqsu3aM3hUykyWW5o1MMGnMsu4c=; b=P5VVzkrnwFhnL8VEFbC8OY9kfDs1xUUmm9PqYXEg9kmNI4IRSl3EPq4rMvuGePQ2sM xKExOIA16zlFQYXygUefOjzi4n3bGmXq4Q094q2HYI/D9uzWI5BxhA9f5kVo7riuJ/U4 BIWYh65HUNT5a1KIql7Dd5kW3LrDU1blca0fzqZFZPByHJSb8gKnf7M6TPFevRguaIY3 7iwq/qBY2u4CBA0Uoz1G8I68kzgZfWdhPQryDVclLfPNlbFJy/nuwcuxSfwdVlfZZtgZ ik2W4KgrXv+zbEnU/rJmlsAgDd269A0824Ysp6pbbjB+BjbGD5l3bhIWHbz3XqD11hdY Uu5g== X-Gm-Message-State: AOAM532pduEClowBW0zv37ulsBXLQtlDoXH90P0BYWuak70STmLbquvJ sO2sGQ4/3Xr2Eku5esf8c9zMqYAmaPG79gfniWaF1LbsFrsdsSoUwmEsixd41GcIp+BqXWH7pqo ta7Sr2ydHCz5aDBSpzw+EZTllEZ/+etIyTgz+2d9NqKM8nPuqS3qAL5aYeQ== X-Received: by 2002:aa7:cd0b:: with SMTP id b11mr29885620edw.412.1643807928850; Wed, 02 Feb 2022 05:18:48 -0800 (PST) X-Received: by 2002:aa7:cd0b:: with SMTP id b11mr29885596edw.412.1643807928661; Wed, 02 Feb 2022 05:18:48 -0800 (PST) MIME-Version: 1.0 References: <00000000000038779505d5d8b372@google.com> In-Reply-To: From: Alexandre Ghiti Date: Wed, 2 Feb 2022 14:18:36 +0100 Message-ID: Subject: Re: [syzbot] riscv/fixes boot error: can't ssh into the instance To: Aleksandr Nogikh Cc: linux-riscv@lists.infradead.org, kasan-dev , palmer@dabbelt.com, syzbot , LKML , syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Aleksandr, On Wed, Feb 2, 2022 at 12:08 PM Aleksandr Nogikh wrote: > > Hello, > > syzbot has already not been able to fuzz its RISC-V instance for 97 That's a longtime, I'll take a look more regularly. > days now because the compiled kernel cannot boot. I bisected the issue > to the following commit: > > commit 54c5639d8f507ebefa814f574cb6f763033a72a5 > Author: Alexandre Ghiti > 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? I'll take a look at that today. Thanks for reporting the issue, Alex > > -- > Best Regards, > Aleksandr > > > On Tue, Jan 18, 2022 at 11:26 AM syzbot > 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.