linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: syzbot <syzbot+4ca3ba1e3ae6ff5ae0f8@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, kuba@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] net build error (6)
Date: Sat, 31 Dec 2022 20:44:15 +0700	[thread overview]
Message-ID: <Y7A8r4Yo07BnDxYv@debian.me> (raw)
In-Reply-To: <0000000000000ad94305f116ba53@google.com>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

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.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2022-12-31 13:44 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 [this message]
2023-01-02  6:36   ` Tetsuo Handa

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=Y7A8r4Yo07BnDxYv@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=davem@davemloft.net \
    --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).