Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <556cb5e5-bfb8-9a2f-054e-e5c8c488a578@kernel.dk>
Date:   Sun, 15 May 2022 11:45:08 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:91.0) Gecko/20100101
 Thunderbird/91.8.1
Subject: Re: [syzbot] WARNING: still has locks held in io_ring_submit_lock
Content-Language: en-US
To:     syzbot <syzbot+987d7bb19195ae45208c@syzkaller.appspotmail.com>,
        asml.silence@gmail.com, f.fainelli@gmail.com,
        io-uring@vger.kernel.org, kuba@kernel.org,
        linux-kernel@vger.kernel.org, olteanv@gmail.com,
        syzkaller-bugs@googlegroups.com, xiam0nd.tong@gmail.com
References: <000000000000873bb305df106d47@google.com>
From:   Jens Axboe <axboe@kernel.dk>
In-Reply-To: <000000000000873bb305df106d47@google.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 5/15/22 11:42 AM, syzbot wrote:
> Hello,
> 
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> WARNING: still has locks held in io_ring_submit_lock

Gah, might help if I actually push out the change...

#syz test: git://git.kernel.dk/linux-block.git for-next

-- 
Jens Axboe