From: Alexandre Ghiti <alex@ghiti.fr>
To: syzbot <syzbot+a74d57bddabbedd75135@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
Subject: Re: [syzbot] riscv/fixes boot error: can't ssh into the instance (2)
Date: Fri, 2 Jun 2023 11:45:13 +0200 [thread overview]
Message-ID: <47f933c3-96db-51c9-2bf2-dc360c4ef261@ghiti.fr> (raw)
In-Reply-To: <811d21e0-3071-d82e-204b-26834eca7b92@ghiti.fr>
On 02/06/2023 09:58, Alexandre Ghiti wrote:
>
> On 01/06/2023 18:04, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 8dc2a7e8027f riscv: Fix relocatable kernels with
>> early alt..
>> 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=17e9fbcd280000
>> kernel config:
>> https://syzkaller.appspot.com/x/.config?x=6b4bf01bbb07f945
>> dashboard link:
>> https://syzkaller.appspot.com/bug?extid=a74d57bddabbedd75135
>> 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
>>
>> Downloadable assets:
>> disk image (non-bootable):
>> https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-8dc2a7e8.raw.xz
>> vmlinux:
>> https://storage.googleapis.com/syzbot-assets/822e3cbe29ad/vmlinux-8dc2a7e8.xz
>> kernel image:
>> https://storage.googleapis.com/syzbot-assets/7bda24abf1c2/Image-8dc2a7e8.xz
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the
>> commit:
>> Reported-by: syzbot+a74d57bddabbedd75135@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 bug is already fixed, let syzbot know by replying with:
>> #syz fix: exact-commit-title
>>
>> If you want to change bug's subsystems, reply with:
>> #syz set subsystems: new-subsystem
>> (See the list of subsystem names on the web dashboard)
>>
>> If the bug is a duplicate of another bug, 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
>
>
> I'm looking into those failures.
So KFENCE was broken by commit 3335068f8721 ("riscv: Use PUD/P4D/PGD
pages for the linear mapping") since our kfence implementation only
breaks pmd hugepages. Let me fix that for 6.4.
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Ghiti <alex@ghiti.fr>
To: syzbot <syzbot+a74d57bddabbedd75135@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
Subject: Re: [syzbot] riscv/fixes boot error: can't ssh into the instance (2)
Date: Fri, 2 Jun 2023 11:45:13 +0200 [thread overview]
Message-ID: <47f933c3-96db-51c9-2bf2-dc360c4ef261@ghiti.fr> (raw)
In-Reply-To: <811d21e0-3071-d82e-204b-26834eca7b92@ghiti.fr>
On 02/06/2023 09:58, Alexandre Ghiti wrote:
>
> On 01/06/2023 18:04, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 8dc2a7e8027f riscv: Fix relocatable kernels with
>> early alt..
>> 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=17e9fbcd280000
>> kernel config:
>> https://syzkaller.appspot.com/x/.config?x=6b4bf01bbb07f945
>> dashboard link:
>> https://syzkaller.appspot.com/bug?extid=a74d57bddabbedd75135
>> 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
>>
>> Downloadable assets:
>> disk image (non-bootable):
>> https://storage.googleapis.com/syzbot-assets/a741b348759c/non_bootable_disk-8dc2a7e8.raw.xz
>> vmlinux:
>> https://storage.googleapis.com/syzbot-assets/822e3cbe29ad/vmlinux-8dc2a7e8.xz
>> kernel image:
>> https://storage.googleapis.com/syzbot-assets/7bda24abf1c2/Image-8dc2a7e8.xz
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the
>> commit:
>> Reported-by: syzbot+a74d57bddabbedd75135@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 bug is already fixed, let syzbot know by replying with:
>> #syz fix: exact-commit-title
>>
>> If you want to change bug's subsystems, reply with:
>> #syz set subsystems: new-subsystem
>> (See the list of subsystem names on the web dashboard)
>>
>> If the bug is a duplicate of another bug, 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
>
>
> I'm looking into those failures.
So KFENCE was broken by commit 3335068f8721 ("riscv: Use PUD/P4D/PGD
pages for the linear mapping") since our kfence implementation only
breaks pmd hugepages. Let me fix that for 6.4.
>
>
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-02 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 16:04 [syzbot] riscv/fixes boot error: can't ssh into the instance (2) syzbot
2023-06-01 16:04 ` syzbot
2023-06-02 7:58 ` Alexandre Ghiti
2023-06-02 7:58 ` Alexandre Ghiti
2023-06-02 9:45 ` Alexandre Ghiti [this message]
2023-06-02 9:45 ` 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=47f933c3-96db-51c9-2bf2-dc360c4ef261@ghiti.fr \
--to=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=syzbot+a74d57bddabbedd75135@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.