From: Niklas Cassel <cassel@kernel.org>
To: "Lai, Yi" <yi1.lai@linux.intel.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
Hannes Reinecke <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Igor Pylypiv <ipylypiv@google.com>,
Niklas Cassel <niklas.cassel@wdc.com>,
linux-ide@vger.kernel.org, yi1.lai@intel.com,
syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data
Date: Tue, 22 Oct 2024 13:04:10 +0200 [thread overview]
Message-ID: <ZxeGqrEpdg9Df5FS@ryzen> (raw)
In-Reply-To: <Zxd2hZWt1zm4eW2q@ly-workstation>
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@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?
> > > >
>
> 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
next prev parent reply other threads:[~2024-10-22 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240909154237.3656000-2-cassel@kernel.org>
2024-10-21 10:58 ` [PATCH v3] ata: libata: Clear DID_TIME_OUT for ATA PT commands with sense data Lai, Yi
2024-10-21 12:07 ` Niklas Cassel
2024-10-21 12:34 ` Damien Le Moal
2024-10-21 15:20 ` Niklas Cassel
2024-10-22 5:44 ` Lai, Yi
2024-10-22 8:48 ` Niklas Cassel
2024-10-22 9:55 ` Lai, Yi
2024-10-22 11:04 ` Niklas Cassel [this message]
2024-10-22 15:59 ` Niklas Cassel
2024-10-23 2:55 ` Lai, Yi
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 \
--in-reply-to=ZxeGqrEpdg9Df5FS@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=ipylypiv@google.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=niklas.cassel@wdc.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yi1.lai@intel.com \
--cc=yi1.lai@linux.intel.com \
/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