Received-SPF: pass (google.com: domain of linux-kernel+bounces-122940-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Message-ID: <271f4b9c-f879-4933-b1e9-1e7481a809eb@ghiti.fr>
Date: Thu, 28 Mar 2024 14:08:30 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [syzbot] riscv/fixes boot error: can't ssh into the instance (3)
Content-Language: en-US
To: syzbot <syzbot+620209d95a0e9fde702f@syzkaller.appspotmail.com>,
 aou@eecs.berkeley.edu, linux-kernel@vger.kernel.org,
 linux-riscv@lists.infradead.org, palmer@dabbelt.com,
 paul.walmsley@sifive.com, syzkaller-bugs@googlegroups.com
References: <0000000000008a75510614b44af1@google.com>
From: Alexandre Ghiti <alex@ghiti.fr>
In-Reply-To: <0000000000008a75510614b44af1@google.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 28/03/2024 09:27, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    653650c468be riscv: Mark __se_sys_* functions __used
> 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=1110f1e6180000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=88360569be845301
> dashboard link: https://syzkaller.appspot.com/bug?extid=620209d95a0e9fde702f
> compiler:       riscv64-linux-gnu-gcc (Debian 12.2.0-13) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: riscv64
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-653650c4.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/2701bf6276c4/vmlinux-653650c4.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/aed54fe6b3d5/Image-653650c4.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+620209d95a0e9fde702f@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.
>
> If the report is already addressed, let syzbot know by replying with:
> #syz fix: exact-commit-title
>
> If you want to overwrite report's subsystems, reply with:
> #syz set subsystems: new-subsystem
> (See the list of subsystem names on the web dashboard)
>
> If the report is a duplicate of another one, reply with:
> #syz dup: exact-subject-of-another-report
>
> If you want to undo deduplication, reply with:
> #syz undup
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv	


So this is fixed by 
https://lore.kernel.org/all/20240326063036.6242-1-osalvador@suse.de/

Here are the relevant syzbot tags (hopefully I get them right):

#syz dup: [syzbot] [mm?] upstream boot error: WARNING: refcount bug in 
__reset_page_owner

#syz fix: mm,page_owner: Fix refcount imbalance

Thanks,

Alex