From: syzbot <syzbot+bc6bfc25a68b7a020ee1@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, jannh@google.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] general protection fault in mas_store_prealloc
Date: Sun, 17 Nov 2024 20:26:02 -0800 [thread overview]
Message-ID: <673ac1da.050a0220.87769.001e.GAE@google.com> (raw)
In-Reply-To: <i2eu66jkrzkudfoa4dmxbxvvsb77pmneou52wg2con6nbdjuov@apux3q3iqjme>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo http://git.infradead.org/users/jedix/linux-maple.git/arm64_kernelci_20241117: failed to run ["git" "fetch" "--force" "9c3e06581107b2a32da6dcbdfdaa1a523995a2c7" "arm64_kernelci_20241117"]: exit status 128
fatal: http://git.infradead.org/users/jedix/linux-maple.git/info/refs not valid: could not determine hash algorithm; is this a git repository?
Tested on:
commit: [unknown
git tree: http://git.infradead.org/users/jedix/linux-maple.git arm64_kernelci_20241117
kernel config: https://syzkaller.appspot.com/x/.config?x=a1eb85a42cb8ccec
dashboard link: https://syzkaller.appspot.com/bug?extid=bc6bfc25a68b7a020ee1
compiler:
userspace arch: arm64
Note: no patches were applied.
next prev parent reply other threads:[~2024-11-18 4:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 10:42 [syzbot] [mm?] general protection fault in mas_store_prealloc syzbot
2024-11-17 18:49 ` Lorenzo Stoakes
2024-11-17 20:32 ` syzbot
2024-11-18 2:49 ` Liam R. Howlett
2024-11-18 13:12 ` Aleksandr Nogikh
2024-11-18 15:21 ` Liam R. Howlett
2024-11-18 15:38 ` Liam R. Howlett
2024-11-18 4:06 ` Liam R. Howlett
2024-11-18 4:26 ` syzbot [this message]
2024-11-18 4:31 ` Liam R. Howlett
2024-11-18 5:04 ` syzbot
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=673ac1da.050a0220.87769.001e.GAE@google.com \
--to=syzbot+bc6bfc25a68b7a020ee1@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
/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.