Theodore Ts'o 47def82672 jbd2: Remove __GFP_NOFAIL from jbd2 layer ...

__GFP_NOFAIL is going away, so add our own retry loop.  Also add
jbd2__journal_start() and jbd2__journal_restart() which take a gfp
mask, so that file systems can optionally (re)start transaction
handles using GFP_KERNEL.  If they do this, then they need to be
prepared to handle receiving an PTR_ERR(-ENOMEM) error, and be ready
to reflect that error up to userspace.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>

2010-07-27 11:56:05 -04:00

..

checkpoint.c

blkdev: generalize flags for blkdev_issue_fn functions

2010-04-28 19:47:36 +02:00

commit.c

blkdev: generalize flags for blkdev_issue_fn functions

2010-04-28 19:47:36 +02:00

journal.c

jbd2: Remove __GFP_NOFAIL from jbd2 layer

2010-07-27 11:56:05 -04:00

Kconfig

Revert "task_struct: make journal_info conditional"

2009-12-17 13:23:24 -08:00

Makefile

…

recovery.c

ext4: remove initialized but not read variables

2010-06-14 13:28:03 -04:00

revoke.c

jbd2: use SWRITE_SYNC_PLUG when writing synchronous revoke records

2009-04-14 07:50:56 -04:00

transaction.c

jbd2: Remove __GFP_NOFAIL from jbd2 layer

2010-07-27 11:56:05 -04:00