diff options
| author | Keith Busch <keith.busch@intel.com> | 2014-07-18 21:40:20 +0400 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2014-11-04 23:17:08 +0300 |
| commit | 302c6727e5eb4d0be0e02d077b65feb3e73ea254 (patch) | |
| tree | 17f37cd779add019ed67a28cb1508e739ff8278a /tools/perf/scripts/python/net_dropmonitor.py | |
| parent | f435c2825b4cc6453b9a1f91418cabbd6ba08cc0 (diff) | |
| download | linux-302c6727e5eb4d0be0e02d077b65feb3e73ea254.tar.xz | |
NVMe: Fix filesystem sync deadlock on removal
This changes the order of deleting the gendisks so it happens after the
nvme IO queues are freed. If a device is removed while a filesystem has
associated dirty data, the removal will wait on these to complete before
proceeding from del_gendisk, which could have caused deadlock before.
The implication of this is that an orderly removal of a responsive
device won't necessarily wait for dirty data to be written, but we are
not guaranteed the device is even going to respond at this point either.
Signed-off-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions