summaryrefslogtreecommitdiffstats
path: root/drivers/block/drbd/drbd_int.h
diff options
context:
space:
mode:
authorLars Ellenberg <lars.ellenberg@linbit.com>2012-09-26 14:18:51 +0200
committerPhilipp Reisner <philipp.reisner@linbit.com>2012-11-09 14:11:39 +0100
commitbc891c9ae3fb2848922e0f0da22fd7de0d58dc1b (patch)
tree58353dfe6fb1257533959a56346b5d5a0a15ad4f /drivers/block/drbd/drbd_int.h
parenta506c13a4d1ec5e1f2f9bc0123dacb5d123004d3 (diff)
downloadblackbird-obmc-linux-bc891c9ae3fb2848922e0f0da22fd7de0d58dc1b.tar.gz
blackbird-obmc-linux-bc891c9ae3fb2848922e0f0da22fd7de0d58dc1b.zip
drbd: fix potential deadlock during bitmap (re-)allocation
The former comment arguing that GFP_KERNEL was good enough was wrong: it did not take resize into account at all, and assumed the only path leading here was the normal attach on a still secondary device, so no deadlock would be possible. Both resize on a Primary, or attach on a diskless Primary, could potentially deadlock. drbd_bm_resize() is called while IO to the respective device is suspended, so we must use GFP_NOIO to avoid potential deadlock. Signed-off-by: Philipp Reisner <philipp.reisner@linbit.com> Signed-off-by: Lars Ellenberg <lars.ellenberg@linbit.com>
Diffstat (limited to 'drivers/block/drbd/drbd_int.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud