linux-kernel - Re: [PATCH v3] ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6cda84ae-c07a-4905-9cf8-12622dab33ee@kernel.org>
Date: Mon, 21 Oct 2024 21:34:56 +0900
From: Damien Le Moal <dlemoal@...nel.org>
To: Niklas Cassel <cassel@...nel.org>, "Lai, Yi" <yi1.lai@...ux.intel.com>
Cc: Hannes Reinecke <hare@...e.de>,
 "Martin K. Petersen" <martin.petersen@...cle.com>,
 Igor Pylypiv <ipylypiv@...gle.com>, Niklas Cassel <niklas.cassel@....com>,
 linux-ide@...r.kernel.org, yi1.lai@...el.com,
 syzkaller-bugs@...glegroups.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] ata: libata: Clear DID_TIME_OUT for ATA PT commands
 with sense data

On 10/21/24 21:07, 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@bytedance.com/
> 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?

s/6.14/6.13 in this paragraph :)

-- 
Damien Le Moal
Western Digital Research