linux-kernel - Re: [syzbot] linux-next build error (13)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <f964a040-b9eb-75ae-ce01-6e8a62dc4d20@infradead.org>
Date:   Tue, 17 May 2022 22:33:52 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     syzbot <syzbot+7013da477748d0b624b9@...kaller.appspotmail.com>,
        axboe@...com, hch@....de, james.smart@...adcom.com,
        kbusch@...nel.org, linux-kernel@...r.kernel.org,
        linux-next@...r.kernel.org, linux-nvme@...ts.infradead.org,
        sagi@...mberg.me, sfr@...b.auug.org.au,
        syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] linux-next build error (13)



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@...kaller.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@...glegroups.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