diff options
| author | Keith Busch <[email protected]> | 2020-04-09 09:08:59 -0700 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2020-05-09 16:18:35 -0600 |
| commit | d567572906d986dedb78b37f111c44eba033f3ef (patch) | |
| tree | a47aac514da6bebf108d485090baac5a9b44bc5b /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | aec459b484b8356d6abe862428787d98ffb1cbde (diff) | |
nvme: unlink head after removing last namespace
The driver had been unlinking the namespace head from the subsystem's
list only after the last reference was released, and outside of the
list's subsys->lock protection.
There is no reason to track an empty head, so unlink the entry from the
subsystem's list when the last namespace using that head is removed and
with the mutex lock protecting the list update. The next namespace to
attach reusing the previous NSID will allocate a new head rather than
find the old head with mismatched identifiers.
Signed-off-by: Keith Busch <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions