From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: davem@davemloft.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
Bagas Sanjaya <bagasdotme@gmail.com>,
syzbot <syzbot+4ca3ba1e3ae6ff5ae0f8@syzkaller.appspotmail.com>
Subject: Re: [syzbot] net build error (6)
Date: Mon, 2 Jan 2023 15:36:54 +0900 [thread overview]
Message-ID: <c9b1c98e-e39c-331e-e22b-69b1e0a59af8@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <Y7A8r4Yo07BnDxYv@debian.me>
On 2022/12/31 22:44, Bagas Sanjaya wrote:
> On Fri, Dec 30, 2022 at 06:46:36PM -0800, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: d3805695fe1e net: ethernet: marvell: octeontx2: Fix uninit..
>> git tree: net
>> console output: https://syzkaller.appspot.com/x/log.txt?x=14f43b54480000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=8ca07260bb631fb4
>> dashboard link: https://syzkaller.appspot.com/bug?extid=4ca3ba1e3ae6ff5ae0f8
>> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+4ca3ba1e3ae6ff5ae0f8@syzkaller.appspotmail.com
>>
>> failed to run ["make" "-j" "64" "ARCH=x86_64" "bzImage"]: exit status 2
>>
>
> I think the actual build warnings/errors should be listed here instead
> of only dumping exit status and then having to click the log output.
>
There is an report which only says "Killed". Possibly terminated by OOM-killer?
Try "dmesg -c > /dev/null" before build and "dmesg" when build failed?
And/or retry build with verbose output?
LD vmlinux.o
Killed
make[1]: *** [scripts/Makefile.vmlinux_o:61: vmlinux.o] Error 137
make[1]: *** Deleting file 'vmlinux.o'
make: *** [Makefile:1245: vmlinux_o] Error 2
prev parent reply other threads:[~2023-01-02 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 2:46 [syzbot] net build error (6) syzbot
2022-12-31 13:44 ` Bagas Sanjaya
2023-01-02 6:36 ` Tetsuo Handa [this message]
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=c9b1c98e-e39c-331e-e22b-69b1e0a59af8@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+4ca3ba1e3ae6ff5ae0f8@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).