From: Theodore Ts'o <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ext4 bug fixes for 3.16
Date: Sun, 29 Jun 2014 20:11:59 -0400 [thread overview]
Message-ID: <20140630001159.GA25311@thunk.org> (raw)
The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:
Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)
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 a93cd4cf86466caa49cfe64607bea7f0bde3f916:
ext4: Fix hole punching for files with indirect blocks (2014-06-26 12:30:54 -0400)
----------------------------------------------------------------
Fix a regression when trying to compile ext4 on older versions gcc.
Fix a number of miscellaneous bugs for punch hole as well as a
long-standing potential double buffer head release when failing a
block allocation for an indirect-mapped file.
----------------------------------------------------------------
Jan Kara (3):
ext4: Fix buffer double free in ext4_alloc_branch()
ext4: Fix block zeroing when punching holes in indirect block files
ext4: Fix hole punching for files with indirect blocks
Namjae Jeon (1):
ext4: decrement free clusters/inodes counters when block group declared bad
T Makphaibulchoke (1):
fs/mbcache: replace __builtin_log2() with ilog2()
fs/ext4/balloc.c | 16 ++++++++++++++++
fs/ext4/ialloc.c | 23 +++++++++++++++++++++++
fs/ext4/indirect.c | 24 +++++++++++++++++++-----
fs/ext4/mballoc.c | 8 ++++++++
fs/mbcache.c | 3 ++-
5 files changed, 68 insertions(+), 6 deletions(-)
next reply other threads:[~2014-06-30 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 0:11 Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-13 20:10 [GIT PULL] ext4 bug fixes for 3.16 Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140630001159.GA25311@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).