[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1111101036160.2338-100000@iolanthe.rowland.org>
Date: Thu, 10 Nov 2011 10:40:21 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Lin Ming <ming.m.lin@...el.com>
cc: linux-kernel@...r.kernel.org, <linux-ide@...r.kernel.org>,
<linux-scsi@...r.kernel.org>, <linux-pm@...r.kernel.org>,
Jeff Garzik <jgarzik@...ox.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
James Bottomley <JBottomley@...allels.com>,
Tejun Heo <tj@...nel.org>, Huang Ying <ying.huang@...el.com>,
Zhang Rui <rui.zhang@...el.com>
Subject: Re: [PATCH v2 4/4] ata: add ata port runtime PM callbacks
On Thu, 10 Nov 2011, Lin Ming wrote:
> Add ata port runtime suspend/resume/idle callbacks.
> Set ->eh_noresume to skip the runtime PM calls on scsi host
> in the error handler to avoid dead lock.
...
> --- a/drivers/ata/libata-scsi.c
> +++ b/drivers/ata/libata-scsi.c
> @@ -3377,6 +3377,7 @@ int ata_scsi_add_hosts(struct ata_host *host, struct scsi_host_template *sht)
> if (!shost)
> goto err_alloc;
>
> + shost->eh_noresume = 1;
> *(struct ata_port **)&shost->hostdata[0] = ap;
> ap->scsi_host = shost;
Are you really sure you want to keep this flag set throughout the
lifetime of the port?
What happens if a command fails, then the port suspends, and then the
error handler is invoked to take care of the failed command?
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists