linux/fs/jbd2
Michal Hocko 7b506b1035 jbd2: get rid of open coded allocation retry loop
insert_revoke_hash does an open coded endless allocation loop if
journal_oom_retry is true. It doesn't implement any allocation fallback
strategy between the retries, though. The memory allocator doesn't know
about the never fail requirement so it cannot potentially help to move
on with the allocation (e.g. use memory reserves).

Get rid of the retry loop and use __GFP_NOFAIL instead. We will lose the
debugging message but I am not sure it is anyhow helpful.

Do the same for journal_alloc_journal_head which is doing a similar
thing.

Signed-off-by: Michal Hocko <mhocko@suse.cz>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2015-06-15 15:45:58 -04:00
..
checkpoint.c jbd2: fix ocfs2 corrupt when updating journal superblock fails 2015-06-15 14:36:01 -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: get rid of open coded allocation retry loop 2015-06-15 15:45:58 -04:00
Kconfig jbd2: remove debug dependency on debug_fs and update Kconfig help text 2013-06-12 23:07:51 -04:00
Makefile [PATCH] jbd2: rename jbd2 symbols to avoid duplication of jbd symbols 2006-10-11 11:14:15 -07:00
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: get rid of open coded allocation retry loop 2015-06-15 15:45:58 -04:00
transaction.c jbd2: speedup jbd2_journal_get_[write|undo]_access() 2015-06-08 12:46:37 -04:00