linux-kernel - Re: [PATCH 0/3] libsas: add support for port multiplier

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 2 May 2014 11:36:17 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Xiangliang Yu <yxlraid@...il.com>
Cc:	JBottomley@...allels.com, dan.j.williams@...el.com,
	todd.e.brandt@...el.com, lukasz.dorau@...el.com,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org
Subject: Re: [PATCH 0/3] libsas: add support for port multiplier

On Thu, Apr 24, 2014 at 09:27:03PM +0800, Xiangliang Yu wrote:
> This patch set will support SATA port multiplier(PM) in LIBSAS. 
> 
> LIBSAS is need to implement several key handling to support SATA PM:
> First,low level driver notify libsas that SATA PM is attached to HBA port.
> Then, LIBSAS will need to schedule SATA PMP error handler to scan SATA device
> that is attached to PM, so we must implemet port softreset and PMP reset 
> handling.
> If find SATA devices, we should add the devices into SAS transport layer.
> In order to find SAS domain device we must implemet device type transformation
> : scsi device -> (port number) -> ata device -> domain device. Then, we can
> execute IO operation.
> 
> In these patches, patch 1 is change SATA error handler.
> And patch 2 will add SATA device into SAS layer and implement device type
> transformation. Patch 3 implement SATA functional interface in mvsas.

Please properly thread the patchset from the next posting.

Dan, can you please take a look at this?

Thanks.

-- 
tejun
--
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/