s390/vfio-ap: check for TAPQ response codes 0x35 and 0x36
authorTony Krowiak <akrowiak@linux.ibm.com>
Tue, 15 Aug 2023 18:43:30 +0000 (14:43 -0400)
committerHeiko Carstens <hca@linux.ibm.com>
Fri, 18 Aug 2023 13:09:29 +0000 (15:09 +0200)
commit7847a19b5b6265f11e71c8499a3b608edac7f398
treec85545905466daad2b205b2fbdfeb5e8c293fd50
parente1f17f8ea93d8fc9d6d0562d38bb0a5fb3e8355e
s390/vfio-ap: check for TAPQ response codes 0x35 and 0x36

Check for response codes 0x35 and 0x36 which are asynchronous return codes
indicating a failure of the guest to associate a secret with a queue. Since
there can be no interaction with this queue from the guest (i.e., the vcpus
are out of SIE for hot unplug, the guest is being shut down or an emulated
subsystem reset of the guest is taking place), let's go ahead and re-issue
the ZAPQ to reset and zeroize the queue.

Signed-off-by: Tony Krowiak <akrowiak@linux.ibm.com>
Reviewed-by: Jason J. Herne <jjherne@linux.ibm.com>
Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
Tested-by: Viktor Mihajlovski <mihajlov@linux.ibm.com>
Link: https://lore.kernel.org/r/20230815184333.6554-10-akrowiak@linux.ibm.com
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
drivers/s390/crypto/vfio_ap_ops.c