linux-kernel - Re: [PATCH 4/4 v4] scsi:stex.c Add S3/S4 support

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <5492454E.8030203@gmail.com>
Date:	Thu, 18 Dec 2014 11:09:02 +0800
From:	Charles Chiou <ch1102chiou@...il.com>
To:	Oliver Neukum <oneukum@...e.de>
CC:	Christoph Hellwig <hch@...radead.org>, JBottomley@...allels.com,
	ed.lin@...mise.com, grace.chang@...promise.com,
	linus.chen@...promise.com, victor.p@...mise.com,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4 v4] scsi:stex.c Add S3/S4 support



On 12/16/2014 05:34 PM, Oliver Neukum wrote:
> On Tue, 2014-12-16 at 14:14 +0800, Charles Chiou wrote:
>>   From f9d84df080c16097218092630db9b5df31d487b5 Mon Sep 17 00:00:00 2001
>> From: Charles Chiou <charles.chiou@...promise.com>
>> Date: Fri, 7 Nov 2014 10:15:18 +0800
>> Subject: [PATCH 4/4] scsi:stex.c Add S3/S4 support
>>
>> Add S3/S4 support, add .suspend and .resume function in pci_driver.
>>
>> Pegasus need 30~40 seconds to boot up. We don't want to OS wait
>> in .resume function. Create a thread to handle device boot up.
>
> I am sorry to be obnoxious, but this patch raises another
> question. What happens if the the system is suspended again
> while the work scheduled in resume is still running?
>
> Furthermore, what happens in the case of a PCI hotunplug while
> the work is still scheduled?
>
> 	Regards
> 		Oliver
>
>

Hi Oliver,
1. When OS is going to suspend again, .suspend function is active,
    and driver prepare a command send to device, while firmware is
    not ready. Firmware might loss this command and host can't go
    to sleep. I'll fix this issue by add while loop to wait device
    ready (polling hba->mu_status) and return -EBUSY if timeout.
    I'll fix this issue in the next version. Thanks for your help.

2. When hotplug, .remove function is active. Return all commands to OS
    with DID_NO_CONNECT status. And OS can remove the driver. After
    experiment, it works well.

BRS
Charles
--
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/