diff options
| author | Lars Ellenberg | 2012-09-26 14:22:40 +0200 |
|---|---|---|
| committer | Philipp Reisner | 2012-11-09 14:11:40 +0100 |
| commit | 8747d30af97232f9ff4cde78b8d259cc715a9b7a (patch) | |
| tree | 4c983fe736a4bdfc80f7a978011d01932ec85e02 /drivers/block/drbd/drbd_worker.c | |
| parent | drbd: fix potential deadlock during bitmap (re-)allocation (diff) | |
| download | kernel-qcow2-linux-8747d30af97232f9ff4cde78b8d259cc715a9b7a.tar.gz kernel-qcow2-linux-8747d30af97232f9ff4cde78b8d259cc715a9b7a.tar.xz kernel-qcow2-linux-8747d30af97232f9ff4cde78b8d259cc715a9b7a.zip | |
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_worker.c')
| -rw-r--r-- | drivers/block/drbd/drbd_worker.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/block/drbd/drbd_worker.c b/drivers/block/drbd/drbd_worker.c index 377f27bbba17..d348260301f1 100644 --- a/drivers/block/drbd/drbd_worker.c +++ b/drivers/block/drbd/drbd_worker.c @@ -473,7 +473,7 @@ struct fifo_buffer *fifo_alloc(int fifo_size) { struct fifo_buffer *fb; - fb = kzalloc(sizeof(struct fifo_buffer) + sizeof(int) * fifo_size, GFP_KERNEL); + fb = kzalloc(sizeof(struct fifo_buffer) + sizeof(int) * fifo_size, GFP_NOIO); if (!fb) return NULL; |