Hidehiro Kawai e9e34f4e8f jbd2: don't abort if flushing file data failed ... In ordered mode, the current jbd2 aborts the journal if a file data buffer has an error. But this behavior is unintended, and we found that it has been adopted accidentally. This patch undoes it and just calls printk() instead of aborting the journal. Unlike a similar patch for ext3/jbd, file data buffers are written via generic_writepages(). But we also need to set AS_EIO into their mappings because wait_on_page_writeback_range() clears AS_EIO before a user process sees it. Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>		2008-07-31 22:26:04 -04:00
..
checkpoint.c	jbd2: Remove data=ordered mode support using jbd buffer heads	2008-07-11 19:27:31 -04:00
commit.c	jbd2: don't abort if flushing file data failed	2008-07-31 22:26:04 -04:00
journal.c	jbd2: Remove data=ordered mode support using jbd buffer heads	2008-07-11 19:27:31 -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: If a journal checksum error is detected, propagate the error to ext4	2008-06-06 17:50:40 -04:00
revoke.c	jdb2: replace remaining __FUNCTION__ occurrences	2008-04-17 10:38:59 -04:00
transaction.c	jbd2: Remove data=ordered mode support using jbd buffer heads	2008-07-11 19:27:31 -04:00