summaryrefslogtreecommitdiff
path: root/drivers/block/drbd/drbd_bitmap.c
diff options
context:
space:
mode:
authorLars Ellenberg <lars.ellenberg@linbit.com>2012-09-26 14:22:40 +0200
committerPhilipp Reisner <philipp.reisner@linbit.com>2012-11-09 14:11:40 +0100
commit8747d30af97232f9ff4cde78b8d259cc715a9b7a (patch)
tree4c983fe736a4bdfc80f7a978011d01932ec85e02 /drivers/block/drbd/drbd_bitmap.c
parentbc891c9ae3fb2848922e0f0da22fd7de0d58dc1b (diff)
downloadlinux-8747d30af97232f9ff4cde78b8d259cc715a9b7a.tar.gz
linux-8747d30af97232f9ff4cde78b8d259cc715a9b7a.tar.xz
drbd: a few more GFP_KERNEL -> GFP_NOIO
This has not yet been observed, but conceivably, when using GFP_KERNEL allocations from drbd_md_sync(), drbd_flush_after_epoch() or receive_SyncParam(), we could trigger additional IO to our own device, or an other device in a criss-cross setup, and end up in a local deadlock, or potentially a distributed deadlock in a criss-cross setup involving the peer blocked in a similar way waiting for us to make progress. 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_bitmap.c')
0 files changed, 0 insertions, 0 deletions