Hi,All
Hello,
On Mon, Jun 20, 2016 at 06:46:55PM -0700, Dan Williams wrote:
On Mon, Jun 20, 2016 at 6:22 PM, Martin K. Petersen
wrote:
"Tejun" == Tejun Heo writes:
In fact,we don't need libata to deal with hotplug in sas environment.
So we
Hello,
On Mon, Jun 20, 2016 at 06:46:55PM -0700, Dan Williams wrote:
> On Mon, Jun 20, 2016 at 6:22 PM, Martin K. Petersen
> wrote:
> >> "Tejun" == Tejun Heo writes:
> >
> >>> In fact,we don't need libata to deal with hotplug in sas environment.
On Mon, Jun 20, 2016 at 6:22 PM, Martin K. Petersen
wrote:
>> "Tejun" == Tejun Heo writes:
>
>>> In fact,we don't need libata to deal with hotplug in sas environment.
>>> So we can't run ata hotplug task when ata port is sas host.
>
> Tejun>
> "Tejun" == Tejun Heo writes:
>> In fact,we don't need libata to deal with hotplug in sas environment.
>> So we can't run ata hotplug task when ata port is sas host.
Tejun> Martin, can you please confirm whether the above is true. If so,
Tejun> I'll route the patch
On Thu, Jun 16, 2016 at 12:45:40PM +0800, DingXiang wrote:
...
> In fact,we don't need libata to deal with hotplug in sas environment.
> So we can't run ata hotplug task when ata port is sas host.
Martin, can you please confirm whether the above is true. If so, I'll
route the patch through
In normal condition,if we use sas protocol and hotplug a
sata disk on a port,the sas driver will send event
"PORTE_BYTES_DMAED" and call function "sas_porte_bytes_dmaed".
But if a sata disk is run io and unplug it,then plug a new
sata disk,this operation may cause a kernel panic like this:
[
6 matches
Mail list logo