From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
syzbot <syzbot+c65436ac3463dd64e422@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] linux-next build error (16)
Date: Thu, 9 Nov 2023 20:10:04 -0800 [thread overview]
Message-ID: <c673ae1d-4eed-4e8e-9772-1de2e67a1d9a@infradead.org> (raw)
In-Reply-To: <20231110122817.47d72603@canb.auug.org.au>
On 11/9/23 17:28, Stephen Rothwell wrote:
> Hi syzbot,
>
> On Thu, 09 Nov 2023 17:08:26 -0800 syzbot <syzbot+c65436ac3463dd64e422@syzkaller.appspotmail.com> wrote:
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: b622d91ca201 Add linux-next specific files for 20231109
>> git tree: linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=16a51397680000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=159f4f31622eb7ff
>> dashboard link: https://syzkaller.appspot.com/bug?extid=c65436ac3463dd64e422
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+c65436ac3463dd64e422@syzkaller.appspotmail.com
>>
>> failed to run ["make" "-j" "64" "ARCH=x86_64" "oldconfig"]: exit status 2
>>
>> ---
>> 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)
>
> #syz set subsystems: crypto
>
This is a kconfig error. Masahiro has dropped the patch that causes it.
https://lore.kernel.org/linux-kbuild/eb9cb563-d480-4000-8feb-b63b856235c3@smile.fr/T/#m8762579bdcc368380788fe7a545e788ddfb306c7
--
~Randy
next prev parent reply other threads:[~2023-11-10 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 1:08 [syzbot] linux-next build error (16) syzbot
2023-11-10 1:28 ` Stephen Rothwell
2023-11-10 4:10 ` Randy Dunlap [this message]
2023-11-10 6:32 ` Stephen Rothwell
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=c673ae1d-4eed-4e8e-9772-1de2e67a1d9a@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+c65436ac3463dd64e422@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).