diff options
| author | Keith Busch <[email protected]> | 2023-07-12 08:36:47 -0700 |
|---|---|---|
| committer | Keith Busch <[email protected]> | 2023-07-12 09:32:58 -0700 |
| commit | 71a5bb153be104d9175636e95166fd5e37466649 (patch) | |
| tree | 43e82166fabb628afe20dd5dbf9cc2209401bfb2 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | ee6fdc5055e916b1dd497f11260d4901c4c1e55e (diff) | |
nvme: ensure disabling pairs with unquiesce
If any error handling that disables the controller fails to queue the
reset work, like if the state changed to disconnected inbetween, then
the failed teardown needs to unquiesce the queues since it's no longer
paired with reset_work. Just make sure that the controller can be put
into a resetting state prior to starting the disable so that no other
handling can change the queue states while recovery is happening.
Reported-by: Ming Lei <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Signed-off-by: Keith Busch <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions