Michal Hocko 6ccaf3e2f3 jbd2: revert must-not-fail allocation loops back to GFP_NOFAIL ... This basically reverts 47def82672 (jbd2: Remove __GFP_NOFAIL from jbd2 layer). The deprecation of __GFP_NOFAIL was a bad choice because it led to open coding the endless loop around the allocator rather than removing the dependency on the non failing allocation. So the deprecation was a clear failure and the reality tells us that __GFP_NOFAIL is not even close to go away. It is still true that __GFP_NOFAIL allocations are generally discouraged and new uses should be evaluated and an alternative (pre-allocations or reservations) should be considered but it doesn't make any sense to lie the allocator about the requirements. Allocator can take steps to help making a progress if it knows the requirements. Signed-off-by: Michal Hocko <mhocko@suse.cz> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Acked-by: David Rientjes <rientjes@google.com>		2015-06-08 10:53:10 -04:00
..
checkpoint.c	jbd2: simplify calling convention around __jbd2_journal_clean_checkpoint_list	2014-09-18 00:58:12 -04:00
commit.c	jbd2: fix descriptor block size handling errors with journal_csum	2014-08-28 22:22:29 -04:00
journal.c	jbd2: revert must-not-fail allocation loops back to GFP_NOFAIL	2015-06-08 10:53:10 -04:00
Kconfig
Makefile
recovery.c	jbd2: fix r_count overflows leading to buffer overflow in journal recovery	2015-05-14 19:11:50 -04:00
revoke.c	jbd2: fix r_count overflows leading to buffer overflow in journal recovery	2015-05-14 19:11:50 -04:00
transaction.c	jbd2: revert must-not-fail allocation loops back to GFP_NOFAIL	2015-06-08 10:53:10 -04:00