1NVME-SECURITY-RECV(1)             NVMe Manual            NVME-SECURITY-RECV(1)
2
3
4

NAME

6       nvme-security-recv - Security Recv command
7

SYNOPSIS

9       nvme security-recv <device> [--size=<size> | -x <size>]
10                           [--secp=<security-protocol> | -p <security-protocol>]
11                           [--spsp=<protocol-specific> | -s <protocol-specific>]
12                           [--nssf=<nvme-specific> | -N <nvme-specific>]
13                           [--al=<allocation-length> | -t <allocation-length>]
14                           [--namespace-id=<nsid> | -n <nsid>]
15                           [--raw-binary | -b]
16

DESCRIPTION

18       The Security Receive command transfers the status and data result of
19       one or more Security Send commands that were previously submitted to
20       the controller.
21
22       The association between a Security Receive command and previous
23       Security Send commands is dependent on the Security Protocol. The
24       format of the data to be transferred is dependent on the Security
25       Protocol. Refer to SPC-4 for Security Protocol details.
26
27       Each Security Receive command returns the appropriate data
28       corresponding to a Security Send command as defined by the rules of the
29       Security Protocol. The Security Receive command data may not be
30       retained if there is a loss of communication between the controller and
31       host, or if a controller reset occurs.
32

OPTIONS

34       -n <nsid>, --namespace-id=<nsid>
35           Target a specific namespace for this security command.
36
37       -N <nssf>, --nssf=<nssf>
38           NVMe Security Specific field. If using security protocol EAh
39           assigned for NVMe use, the NVMe security specific field indicates
40           which reply memory buffer target.
41
42       -x <size>, --size=<size>
43           Size of buffer to allocate. One success it will be printed to
44           STDOUT.
45
46       -p <security-protocol>, --secp=<security-protocol>
47           Security Protocol: This field specifies the security protocol as
48           defined in SPC-4. The controller shall fail the command with
49           Invalid Parameter indicated if a reserved value of the Security
50           Protocol is specified.
51
52       -s <security-protocol-specific>, --spsp=<security-protocol-specific>
53           SP Specific: The value of this field is specific to the Security
54           Protocol as defined in SPC-4.
55
56       -t <allocation-length>, --al=<allocation-length>
57           Allocation Length: The value of this field is specific to the
58           Security Protocol as defined in SPC-4.
59
60       -b, --raw-binary
61           Print the raw buffer to stdout. Defaults to print in hex.
62

EXAMPLES

64       No Examples
65

NVME

67       Part of the nvme-user suite
68
69
70
71NVMe                              06/05/2018             NVME-SECURITY-RECV(1)
Impressum