public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: syzbot <[email protected]>,
	[email protected], [email protected],
	[email protected], [email protected],
	[email protected], [email protected],
	[email protected], [email protected]
Subject: Re: [syzbot] WARNING: still has locks held in io_ring_submit_lock
Date: Sun, 15 May 2022 11:22:56 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

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 <[email protected]>
> 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


  reply	other threads:[~2022-05-15 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 14:52 [syzbot] WARNING: still has locks held in io_ring_submit_lock syzbot
2022-05-15 17:22 ` Jens Axboe [this message]
2022-05-15 17:42   ` syzbot
2022-05-15 17:45     ` Jens Axboe
2022-05-15 18:06       ` syzbot

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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