public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Li Nan <linan666@huaweicloud.com>
Cc: "dlemoal@kernel.org" <dlemoal@kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"yukuai3@huawei.com" <yukuai3@huawei.com>,
	"yi.zhang@huawei.com" <yi.zhang@huawei.com>,
	"houtao1@huawei.com" <houtao1@huawei.com>,
	"yangerkun@huawei.com" <yangerkun@huawei.com>
Subject: Re: [PATCH] scsi: ata: Fix a race condition between scsi error handler and ahci interrupt
Date: Tue, 22 Aug 2023 10:30:14 +0000	[thread overview]
Message-ID: <ZOSONbLwc6RtQnS0@x1-carbon> (raw)
In-Reply-To: <f33816ef-ce26-1501-99b6-c75f91c6d8f5@huaweicloud.com>

On Tue, Aug 22, 2023 at 05:20:33PM +0800, Li Nan wrote:
> Thanks for your reply, Niklas.
> 
> 在 2023/8/21 21:51, Niklas Cassel 写道:
> > On Thu, Aug 10, 2023 at 09:48:48AM +0800, linan666@huaweicloud.com wrote:
> 
> [snip]
> 
> > 
> > Hello Li Nan,
> > 
> > I do not understand why the code in:
> > https://github.com/torvalds/linux/blob/v6.5-rc7/drivers/ata/libata-eh.c#L722-L731
> > 
> > does not kick in, and repeats EH.
> > 
> > 
> > EH_PENDING is cleared before ->error_handler() is called:
> > https://github.com/torvalds/linux/blob/v6.5-rc7/drivers/ata/libata-eh.c#L697
> > 
> > So ahci_error_intr() from the second error interrupt, which is called after
> > thawing the port, should have called ata_std_sched_eh(), which calls
> > ata_eh_set_pending(), which should have set EH_PENDING:
> > https://github.com/torvalds/linux/blob/v6.5-rc7/drivers/ata/libata-eh.c#L884
> > 
> > 
> > 
> > My only guess is that after thawing the port:
> > https://github.com/torvalds/linux/blob/v6.5-rc7/drivers/ata/libata-eh.c#L2807
> > 
> > The second error irq comes, and sets EH_PENDING,
> > but then this silly code might clear it:
> > https://github.com/torvalds/linux/blob/v6.5-rc7/drivers/ata/libata-eh.c#L2825-L2837
> > 
> 
> Yeah, I think so.
> 
> > I think the best way would be if we could improve this "spurious error
> > condition check"... because if this is indeed the code that clears EH_PENDING
> > for you, then this code basically makes the "goto repeat" code in
> > ata_scsi_port_error_handler() useless...
> > 
> > 
> > An alternative to improving the "spurious error condition check" might be for
> > you to try something like:
> > 
> 
> We have used this solution before, but it will case WARN_ON in
> ata_eh_finish() as below:
> 
>   WARNING: CPU: 1 PID: 118 at ../drivers/ata/libata-eh.c:4016
> ata_eh_finish+0x15a/0x170

Ok.

How about if you simply move the WARN_ON to ata_scsi_port_error_handler()
as well:

diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c
index 35e03679b0bf..5be2fc651131 100644
--- a/drivers/ata/libata-eh.c
+++ b/drivers/ata/libata-eh.c
@@ -741,6 +741,12 @@ void ata_scsi_port_error_handler(struct Scsi_Host *host, struct ata_port *ap)
                 */
                ap->ops->end_eh(ap);
 
+               if (!ap->scsi_host->host_eh_scheduled) {
+                       /* make sure nr_active_links is zero after EH */
+                       WARN_ON(ap->nr_active_links);
+                       ap->nr_active_links = 0;
+               }
+
                spin_unlock_irqrestore(ap->lock, flags);
                ata_eh_release(ap);
        } else {
@@ -962,7 +968,7 @@ void ata_std_end_eh(struct ata_port *ap)
 {
        struct Scsi_Host *host = ap->scsi_host;
 
-       host->host_eh_scheduled = 0;
+       host->host_eh_scheduled--;
 }
 EXPORT_SYMBOL(ata_std_end_eh);
 
@@ -3948,10 +3954,6 @@ void ata_eh_finish(struct ata_port *ap)
                        }
                }
        }
-
-       /* make sure nr_active_links is zero after EH */
-       WARN_ON(ap->nr_active_links);
-       ap->nr_active_links = 0;
 }
 
 /**



Kind regards,
Niklas

  reply	other threads:[~2023-08-22 10:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10  1:48 [PATCH] scsi: ata: Fix a race condition between scsi error handler and ahci interrupt linan666
2023-08-10  2:49 ` Damien Le Moal
2023-08-14  6:41   ` Li Nan
2023-08-14  7:50     ` Damien Le Moal
2023-08-14 13:20       ` Li Nan
2023-08-15  2:41         ` Damien Le Moal
2023-08-17  7:41           ` Li Nan
2023-08-21 13:51 ` Niklas Cassel
2023-08-22  9:20   ` Li Nan
2023-08-22 10:30     ` Niklas Cassel [this message]
2023-09-04 11:45       ` Li Nan
2023-09-04 11:57         ` Niklas Cassel
2023-09-04 13:00           ` Li Nan

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=ZOSONbLwc6RtQnS0@x1-carbon \
    --to=niklas.cassel@wdc.com \
    --cc=dlemoal@kernel.org \
    --cc=houtao1@huawei.com \
    --cc=linan666@huaweicloud.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.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