summaryrefslogtreecommitdiffstats
path: root/drivers/vfio
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.com>2017-10-17 13:46:43 +1100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-07-08 15:30:50 +0200
commitfeabea21655961e6b0f87ad7351a4f99515c6b09 (patch)
tree16cee3bcd7dc566c29abd8a66ffac7c745c7ab9f /drivers/vfio
parentcc091f3fbbdb117d819536d6249e34322f991899 (diff)
downloadlinux-stable-feabea21655961e6b0f87ad7351a4f99515c6b09.tar.gz
linux-stable-feabea21655961e6b0f87ad7351a4f99515c6b09.tar.bz2
linux-stable-feabea21655961e6b0f87ad7351a4f99515c6b09.zip
md: move suspend_hi/lo handling into core md code
commit b3143b9a38d5039bcd1f2d1c94039651bfba8043 upstream. responding to ->suspend_lo and ->suspend_hi is similar to responding to ->suspended. It is best to wait in the common core code without incrementing ->active_io. This allows mddev_suspend()/mddev_resume() to work while requests are waiting for suspend_lo/hi to change. This is will be important after a subsequent patch which uses mddev_suspend() to synchronize updating for suspend_lo/hi. So move the code for testing suspend_lo/hi out of raid1.c and raid5.c, and place it in md.c Signed-off-by: NeilBrown <neilb@suse.com> Signed-off-by: Shaohua Li <shli@fb.com> Signed-off-by: Jack Wang <jinpu.wang@profitbricks.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/vfio')
0 files changed, 0 insertions, 0 deletions