[GIT PULL] ext4 bug fixes for 3.17

From: Theodore Ts'o
Date: Thu Aug 28 2014 - 22:48:47 EST


The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:

Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)

are available in the git repository at:

git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable

for you to fetch changes up to d80d448c6c5bdd32605b78a60fe8081d82d4da0f:

ext4: fix same-dir rename when inline data directory overflows (2014-08-28 22:22:29 -0400)

----------------------------------------------------------------
Ext4 bug fixes for 3.17, to provide better handling of memory
allocation failures, and to fix some journaling bugs involving journal
checksums and FALLOC_FL_ZERO_RANGE.

----------------------------------------------------------------
Darrick J. Wong (3):
jbd2: fix infinite loop when recovering corrupt journal blocks
jbd2: fix descriptor block size handling errors with journal_csum
ext4: fix same-dir rename when inline data directory overflows

Dmitry Monakhov (4):
ext4: move i_size,i_disksize update routines to helper function
ext4: fix incorect journal credits reservation in ext4_zero_range
ext4: fix transaction issues for ext4_fallocate and ext_zero_range
ext4: update i_disksize coherently with block allocation on error path

Theodore Ts'o (2):
ext4: propagate errors up to ext4_find_entry()'s callers
ext4: fix BUG_ON in mb_free_blocks()

fs/ext4/ext4.h | 18 ++++++++++-
fs/ext4/extents.c | 88 +++++++++++++++++++++++++++---------------------------
fs/ext4/inode.c | 44 ++++++++++-----------------
fs/ext4/mballoc.c | 5 ++++
fs/ext4/namei.c | 56 ++++++++++++++++++++++++++++++----
fs/ext4/super.c | 5 ++--
fs/jbd2/commit.c | 21 +++++++------
fs/jbd2/journal.c | 56 ++++++++++++++++++++++------------
fs/jbd2/recovery.c | 33 ++++++++++++--------
fs/jbd2/revoke.c | 6 ++--
include/linux/jbd2.h | 30 +++++++++++++++----
11 files changed, 233 insertions(+), 129 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/