On Tue, Oct 22, 2024 at 05:55:17PM +0800, Lai, Yi wrote: > On Tue, Oct 22, 2024 at 10:48:04AM +0200, Niklas Cassel wrote: > > On Tue, Oct 22, 2024 at 01:44:08PM +0800, Lai, Yi wrote: > > > On Mon, Oct 21, 2024 at 05:20:12PM +0200, Niklas Cassel wrote: > > > > On Mon, Oct 21, 2024 at 02:07:21PM +0200, Niklas Cassel wrote: > > > > > Hello Yi Lai, > > > > > > > > > > On Mon, Oct 21, 2024 at 06:58:59PM +0800, Lai, Yi wrote: > > > > > > Hi Niklas Cassel, > > > > > > > > > > > > Greetings! > > > > > > > > > > > > I used Syzkaller and found that there is INFO: task hung in blk_mq_get_tag in v6.12-rc3 > > > > > > > > > > > > After bisection and the first bad commit is: > > > > > > " > > > > > > e5dd410acb34 ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data > > > > > > " > > > > > > > > > > It might be that your bisection results are accurate. > > > > > > > > > > However, after looking at the stacktraces, I find it way more likely that > > > > > bisection has landed on the wrong commit. > > > > > > > > > > See this series that was just queued (for 6.13) a few days ago that solves a > > > > > similar starvation: > > > > > https://lore.kernel.org/linux-block/20241014092934.53630-1-songmuchun@xxxxxxxxxxxxx/ > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/log/?h=for-6.13/block > > > > > > > > > > You could perhaps run with v6.14-rc4 (which should be able to trigger the bug) > > > > > and then try v6.14-rc4 + that series applied, to see if you can still trigger > > > > > the bug? > > > > > > I tried kernel linux-block > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git > branch for-6.13/block commit c97f91b1807a7966077b69b24f28c2dbcde664e9. > > Issue can still be reproduced. Thanks again for your testing! I will try to reproduce using your reproducer (repo.c), and see if I can make any sense of this. Kind regards, Niklas
