From: syzbot <syzbot+c793a7eca38803212c61@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, marcello.bauer@9elements.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] INFO: rcu detected stall in schedule_timeout (6)
Date: Tue, 25 Jun 2024 04:31:02 -0700 [thread overview]
Message-ID: <0000000000008e2400061bb53bba@google.com> (raw)
In-Reply-To: <dd54a706e0d5ba7cb01e073a256b6855409684db.camel@9elements.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
kernel clean failed: failed to run ["make" "-j" "64" "ARCH=x86_64" "distclean"]: exit status 2
Makefile:83: *** Cannot find a vmlinux for VMLINUX_BTF at any of " ../../vmlinux /sys/kernel/btf/vmlinux /boot/vmlinux-5.9.0-0.bpo.5-cloud-amd64". Stop.
make[2]: *** [Makefile:192: sched_ext_clean] Error 2
make[1]: *** [/syzkaller/jobs-2/linux/kernel/Makefile:1361: sched_ext] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:240: __sub-make] Error 2
Tested on:
commit: 62c97045 Add linux-next specific files for 20240624
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=ccdd3ebd6715749a
dashboard link: https://syzkaller.appspot.com/bug?extid=c793a7eca38803212c61
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=16f96f51980000
next parent reply other threads:[~2024-06-25 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd54a706e0d5ba7cb01e073a256b6855409684db.camel@9elements.com>
2024-06-25 11:31 ` syzbot [this message]
[not found] <167e42c556fa9f7e59f8ada1957d17f950befa42.camel@9elements.com>
2024-07-08 12:57 ` [syzbot] [usb?] INFO: rcu detected stall in schedule_timeout (6) syzbot
[not found] <b4ace972d8d8125d04851f9961399270fa297747.camel@9elements.com>
2024-06-25 9:22 ` syzbot
2024-05-16 19:17 syzbot
2024-05-16 22:01 ` syzbot
2024-06-04 12:05 ` Marcello Sylvester Bauer
2024-06-04 14:20 ` Alan Stern
2024-05-16 22:28 ` Hillf Danton
2024-05-17 0:18 ` 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=0000000000008e2400061bb53bba@google.com \
--to=syzbot+c793a7eca38803212c61@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcello.bauer@9elements.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