diff options
| author | Lars Ellenberg <lars.ellenberg@linbit.com> | 2012-09-20 14:24:20 +0200 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2012-10-30 08:39:18 +0100 |
| commit | 8b45a5c8a190d0ea0077928fd8e95c0752e40e41 (patch) | |
| tree | 181d93830f9bc482496548584b7b5137a04b3119 /drivers/block/drbd/drbd_bitmap.c | |
| parent | 0b143d4382b62db6738196caaefa793e5c0f6690 (diff) | |
| download | linux-stable-8b45a5c8a190d0ea0077928fd8e95c0752e40e41.tar.gz linux-stable-8b45a5c8a190d0ea0077928fd8e95c0752e40e41.tar.bz2 linux-stable-8b45a5c8a190d0ea0077928fd8e95c0752e40e41.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>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/block/drbd/drbd_bitmap.c')
0 files changed, 0 insertions, 0 deletions