nvme-fabrics: clarify AUTHREQ result handling
authorHannes Reinecke <hare@suse.de>
Thu, 8 Dec 2022 07:49:20 +0000 (08:49 +0100)
committerChristoph Hellwig <hch@lst.de>
Wed, 1 Feb 2023 13:21:58 +0000 (14:21 +0100)
commit0686fb3cc535c4c1685553c56f4efe3eeee57b09
tree7e00b4217058e162aad338b4108186537e0595e2
parent2d97930d74b12467fd5f48d8560e48c1cf5edcb1
nvme-fabrics: clarify AUTHREQ result handling

The NVMe 2.0 spec defines the ATR and ASCR bits in the AUTHREQ
connect response field to be mutually exclusive. So to clarify the
handling here switch the AUTHREQ handling to use the bit definitions
and check for both bits.
And while we're at it, add a message to the user that secure
concatenation is not supported (yet).

Suggested-by: Mark Lehrer <mark.lehrer@wdc.com>
Signed-off-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
drivers/nvme/host/fabrics.c