Annie Li dc52d783d6 xen-blkback: stop blkback thread of every queue in xen_blkif_disconnect ...

In xen_blkif_disconnect, before checking inflight I/O, following code
stops the blkback thread,
if (ring->xenblkd) {
	kthread_stop(ring->xenblkd);
	wake_up(&ring->shutdown_wq);
}
If there is inflight I/O in any non-last queue, blkback returns -EBUSY
directly, and above code would not be called to stop thread of remaining
queue and processs them. When removing vbd device with lots of disk I/O
load, some queues with inflight I/O still have blkback thread running even
though the corresponding vbd device or guest is gone.
And this could cause some problems, for example, if the backend device type
is file, some loop devices and blkback thread always lingers there forever
after guest is destroyed, and this causes failure of umounting repositories
unless rebooting the dom0.
This patch allows thread of every queue has the chance to get stopped.
Otherwise, only thread of queue previous to(including) first busy one get
stopped, blkthread of remaining queue will still run.  So stop all threads
properly and return -EBUSY if any queue has inflight I/O.

Signed-off-by: Annie Li <annie.li@oracle.com>
Reviewed-by: Herbert van den Bergh <herbert.van.den.bergh@oracle.com>
Reviewed-by: Bhavesh Davda <bhavesh.davda@oracle.com>
Reviewed-by: Adnan Misherfi <adnan.misherfi@oracle.com>
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

2017-08-25 15:59:34 -04:00

..

blkback.c

Merge commit '8e8320c9315c' into for-4.13/block

2017-06-22 21:55:24 -06:00

common.h

xen-blkback: don't leak stack data via response ring

2017-06-13 16:28:32 -04:00

Makefile

xen/blkback: Squash vbd.c,interface.c in blkback.c and xenbus.c respectivly.

2011-04-20 11:57:59 -04:00

xenbus.c

xen-blkback: stop blkback thread of every queue in xen_blkif_disconnect

2017-08-25 15:59:34 -04:00