[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <de26ea1c-c263-0418-ba79-e9dfa85a3abd@kernel.dk>
Date: Sun, 15 May 2022 11:22:56 -0600
From: Jens Axboe <axboe@...nel.dk>
To: syzbot <syzbot+987d7bb19195ae45208c@...kaller.appspotmail.com>,
asml.silence@...il.com, f.fainelli@...il.com,
io-uring@...r.kernel.org, kuba@...nel.org,
linux-kernel@...r.kernel.org, olteanv@...il.com,
syzkaller-bugs@...glegroups.com, xiam0nd.tong@...il.com
Subject: Re: [syzbot] WARNING: still has locks held in io_ring_submit_lock
On 5/15/22 8:52 AM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 1e1b28b936ae Add linux-next specific files for 20220513
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=10872211f00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e4eb3c0c4b289571
> dashboard link: https://syzkaller.appspot.com/bug?extid=987d7bb19195ae45208c
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1141bd21f00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167ebdbef00000
>
> The issue was bisected to:
>
> commit 6da69b1da130e7d96766042750cd9f902e890eba
> Author: Xiaomeng Tong <xiam0nd.tong@...il.com>
> Date: Mon Mar 28 03:24:31 2022 +0000
>
> net: dsa: bcm_sf2_cfp: fix an incorrect NULL check on list iterator
That looks totally unrelated...
#syz test: git://git.kernel.dk/linux-block.git for-next
--
Jens Axboe
Powered by blists - more mailing lists