From: Randy Dunlap <rdunlap@infradead.org>
To: syzbot <syzbot+7013da477748d0b624b9@syzkaller.appspotmail.com>,
axboe@fb.com, hch@lst.de, james.smart@broadcom.com,
kbusch@kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, linux-nvme@lists.infradead.org,
sagi@grimberg.me, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] linux-next build error (13)
Date: Tue, 17 May 2022 22:33:52 -0700 [thread overview]
Message-ID: <f964a040-b9eb-75ae-ce01-6e8a62dc4d20@infradead.org> (raw)
In-Reply-To: <000000000000b3a1f405df33be01@google.com>
On 5/17/22 04:50, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 47c1c54d1bcd Add linux-next specific files for 20220517
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=137f0301f00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=95ad7f734b04ada9
> dashboard link: https://syzkaller.appspot.com/bug?extid=7013da477748d0b624b9
> 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+7013da477748d0b624b9@syzkaller.appspotmail.com
>
> drivers/nvme/host/fc.c:1914: undefined reference to `blkcg_get_fc_appid'
>
> ---
> 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.
Fix is here:
https://lore.kernel.org/lkml/e2f636e1-33ff-3d9f-a793-960f239d0bc2@infradead.org/T/#m2cca6716362ec3f367d15798c0af05f6c3f879a0
--
~Randy
prev parent reply other threads:[~2022-05-18 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 11:50 syzbot
2022-05-18 5:33 ` Randy Dunlap [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=f964a040-b9eb-75ae-ce01-6e8a62dc4d20@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+7013da477748d0b624b9@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
all inboxes | Powered by JetHome®