There is no need to wake up xen_blkif_schedule() as kthread_stop() is able
to already wake up the kernel thread.
Signed-off-by: Dongli Zhang <dongli.zh...@oracle.com>
---
drivers/block/xen-blkback/xenbus.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/block/xen-blkback/xenbus.c
b/drivers/block/xen-blkback/xenbus.c
index a4bc74e..37ac59e 100644
--- a/drivers/block/xen-blkback/xenbus.c
+++ b/drivers/block/xen-blkback/xenbus.c
@@ -254,10 +254,8 @@ static int xen_blkif_disconnect(struct xen_blkif *blkif)
if (!ring->active)
continue;
- if (ring->xenblkd) {
+ if (ring->xenblkd)
kthread_stop(ring->xenblkd);
- wake_up(&ring->shutdown_wq);
- }
/* The above kthread_stop() guarantees that at this point we
* don't have any discard_io or other_io requests. So, checking
--
2.7.4
