diff options
| author | Tony Krowiak <[email protected]> | 2023-08-15 14:43:30 -0400 |
|---|---|---|
| committer | Heiko Carstens <[email protected]> | 2023-08-18 15:09:29 +0200 |
| commit | 7847a19b5b6265f11e71c8499a3b608edac7f398 (patch) | |
| tree | c85545905466daad2b205b2fbdfeb5e8c293fd50 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | e1f17f8ea93d8fc9d6d0562d38bb0a5fb3e8355e (diff) | |
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 <[email protected]>
Reviewed-by: Jason J. Herne <[email protected]>
Reviewed-by: Halil Pasic <[email protected]>
Tested-by: Viktor Mihajlovski <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Heiko Carstens <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions