Mikulas Patocka a72986c562 dm raid1: keep retrying alloc if mempool_alloc failed
If the code can't handle allocation failures, use __GFP_NOFAIL so that
in case of memory pressure the allocator will retry indefinitely and
won't return NULL which would cause a crash in the function.

This is still not a correct fix, it may cause a classic deadlock when
memory manager waits for I/O being done and I/O waits for some free memory.
I/O code shouldn't allocate any memory. But in this case it probably
doesn't matter much in practice, people usually do not swap on RAID.

Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
2009-06-22 10:12:13 +01:00
..
2009-06-16 19:50:13 -07:00
2009-06-18 09:56:20 +02:00
2009-06-17 11:06:25 +01:00
2009-06-16 19:50:13 -07:00
2009-06-17 09:35:24 -07:00
2009-06-19 10:29:20 +10:00
2009-06-16 19:50:13 -07:00
2009-06-18 13:04:04 -07:00
2009-05-07 17:28:59 +02:00
2009-06-17 14:04:42 -07:00
2009-06-16 19:50:13 -07:00
2009-06-18 13:04:04 -07:00
2009-06-15 16:47:25 +10:00
2009-06-19 16:46:05 -07:00
2009-06-19 11:04:32 -07:00
2009-06-18 13:04:04 -07:00
2009-06-18 13:04:04 -07:00