[nvmewin] Zero Length for Security Receive and Security Send command

[Robles, Raymond C]

Yun,

Your patch is now in line to be reviewed.

Reviewing Companies,

Please review Yun's patch for zero length Secure Send/Receive commands and provide feedback on or before September 4th. Thanks!

Thanks,
Ray

From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Robles, Raymond C
Sent: Thursday, July 30, 2015 3:25 PM
To: Yun Wang
Cc: nvmewin at lists.openfabrics.org
Subject: Re: [nvmewin] Zero Length for Security Receive and Security Send command

Hi Yun,

Thank you for your patch submission. There is one patch in front of yours. Once that patch has been reviewed and approved, your patch will be reviewed next.

Thanks,
Ray

From: nvmewin-bounces at lists.openfabrics.org<mailto:nvmewin-bounces at lists.openfabrics.org> [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Yun Wang
Sent: Friday, July 24, 2015 6:00 PM
To: nvmewin at lists.openfabrics.org<mailto:nvmewin at lists.openfabrics.org>
Subject: [nvmewin] Zero Length for Security Receive and Security Send command

Hi:

Current OFA driver doesn't allow zero length for Security Receive and Security Send command.

Per NVMe spec., "Security Receive command with the Security Protocol field set to 00h shall return information about the security protocols supported by the controller. This command is used in the security discovery process and is not associated with a Security Send command. Refer to SPC-4 for the details of Security Protocol 00h and the SP Specific field".
Per SPC-4 spec., "a transfer length of zero specifies that no data transfer shall take place. This condition shall not be considered an error", zero length of data transfer for Security Protocol 00h should be allowed.
On the other hand,  for some practices with other Security Protocol, zero length will be needed, too.

This patch is to allow zero length of data transfer for Security Receive and Security Send command. It has been tested over Win8.1 x64 platform and works as expected. Please review and help merge it into the trunk.

The password for the attachment is nvme_sec.

Best Regards,
Yun Wang
ULINK Technology, Inc.
Website: www.ulinktech.com<www.ulinktech.com%20>
Office: +1(408) 446-8455
Email: yun.wang at ulinktech.com<mailto:joseph.chen at ulinktech.com>
[ulink logo 2]<http://www.ulinktech.com/>
DISCLAIMER: The information contained in this message is confidential and may be legally privileged. If you are not the intended recipient (or have received this e-mail in error), please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150824/a0ec179d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1628 bytes
Desc: image001.jpg
URL: <http://lists.openfabrics.org/pipermail/nvmewin/attachments/20150824/a0ec179d/attachment.jpg>