diff options
| author | Keith Busch <[email protected]> | 2023-10-27 10:58:12 -0700 |
|---|---|---|
| committer | Keith Busch <[email protected]> | 2023-12-04 08:39:03 -0800 |
| commit | e6e7f7ac03e40795346f1b2994a05f507ad8d345 (patch) | |
| tree | 3e48f621f67d05ce07d4c6f71b6ac16a1f346206 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 5c687c287c46fadb14644091823298875a5216aa (diff) | |
nvme: ensure reset state check ordering
A different CPU may be setting the ctrl->state value, so ensure proper
barriers to prevent optimizing to a stale state. Normally it isn't a
problem to observe the wrong state as it is merely advisory to take a
quicker path during initialization and error recovery, but seeing an old
state can report unexpected ENETRESET errors when a reset request was in
fact successful.
Reported-by: Minh Hoang <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Signed-off-by: Keith Busch <[email protected]>
Signed-off-by: Hannes Reinecke <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions