Varun Prakash f614b937d8 nvmet-tcp: handle ICReq PDU received in NVMET_TCP_Q_LIVE state ... As per NVMe/TCP transport specification ICReq PDU is the first PDU received by the controller and controller should receive only one ICReq PDU. If controller receives more than one ICReq PDU then this can be considered as fatal error. nvmet-tcp driver does not check for ICReq PDU opcode if queue state is NVMET_TCP_Q_LIVE. In LIVE state ICReq PDU is treated as CapsuleCmd PDU, this can result in abnormal behavior. Add a check for ICReq PDU in nvmet_tcp_done_recv_pdu() to fix this issue. Signed-off-by: Varun Prakash <varun@chelsio.com> Reviewed-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Christoph Hellwig <hch@lst.de>		2022-09-27 09:22:08 +02:00
..
common	nvmet-auth: fix a couple of spelling mistakes	2022-08-02 17:22:51 -06:00
host	nvme-pci: report the actual number of tagset maps	2022-09-27 09:22:07 +02:00
target	nvmet-tcp: handle ICReq PDU received in NVMET_TCP_Q_LIVE state	2022-09-27 09:22:08 +02:00
Kconfig	nvme: implement In-Band authentication	2022-08-02 17:14:49 -06:00
Makefile	nvme: implement In-Band authentication	2022-08-02 17:14:49 -06:00