Message-ID: <5ff2b3c0-eb96-c423-dcee-1bdf6604e9df@kernel.dk>
Date:   Wed, 1 Mar 2023 07:53:57 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101
 Thunderbird/102.8.0
Subject: Re: INFO: task hung in io_ring_exit_work
Content-Language: en-US
To:     Sanan Hasanov <sanan.hasanov@Knights.ucf.edu>,
        "asml.silence@gmail.com" <asml.silence@gmail.com>,
        "io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc:     "syzkaller@googlegroups.com" <syzkaller@googlegroups.com>,
        "contact@pgazz.com" <contact@pgazz.com>
References: <IA1PR07MB9830E72E8A3426B8151185BAABAF9@IA1PR07MB9830.namprd07.prod.outlook.com>
From:   Jens Axboe <axboe@kernel.dk>
In-Reply-To: <IA1PR07MB9830E72E8A3426B8151185BAABAF9@IA1PR07MB9830.namprd07.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 2/26/23 11:23 PM, Sanan Hasanov wrote:
> Good day, dear maintainers,
> 
> We found a bug using a modified kernel configuration file used by syzbot.
> 
> We enhanced the coverage of the configuration file using our tool, klocalizer.
> 
> Kernel Branch: 6.2.0-next-20230225
> Kernel config: https://drive.google.com/file/d/1NS9N8rvftQ7BouImn2OVnC96qrNhAeuO/view?usp=share_link
> C Reproducer: Unfortunately, there is no reproducer for this bug yet.

Not sure what we're supposed to do with this, without a syzbot or
c reproducer? You can get into this condition if you SIGSTOP the
task so it can't complete its task_work, for example. But impossible
to glean anything from this report.

-- 
Jens Axboe