summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorKeith Busch <keith.busch@intel.com>2014-07-18 11:40:20 -0600
committerJens Axboe <axboe@fb.com>2014-11-04 13:17:08 -0700
commit302c6727e5eb4d0be0e02d077b65feb3e73ea254 (patch)
tree17f37cd779add019ed67a28cb1508e739ff8278a /scripts
parentf435c2825b4cc6453b9a1f91418cabbd6ba08cc0 (diff)
downloadop-kernel-dev-302c6727e5eb4d0be0e02d077b65feb3e73ea254.zip
op-kernel-dev-302c6727e5eb4d0be0e02d077b65feb3e73ea254.tar.gz
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 'scripts')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud