From: Theodore Ts'o <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [GIT PULL] ext4 bug fixes for 3.20-rc1
Date: Sun, 22 Feb 2015 18:01:04 -0500 [thread overview]
Message-ID: <20150222230104.GA16515@thunk.org> (raw)
The following changes since commit 3b421b80be635d696848b72d3c7700a0e5ee3414:
Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2015-01-06 14:05:40 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus
for you to fetch changes up to 6f30b7e37a8239f9d27db626a1d3427bc7951908:
ext4: fix indirect punch hole corruption (2015-02-14 20:08:51 -0500)
----------------------------------------------------------------
Ext4 bug fixes for 3.20. We also reserved code points for encryption
and read-only images (for which the implementation is mostly just the
reserved code point for a read-only feature :-)
----------------------------------------------------------------
Darrick J. Wong (2):
jbd2: complain about descriptor block checksum errors
ext4: support read-only images
Eric Sandeen (2):
ext4: remove duplicate remount check for JOURNAL_CHECKSUM change
ext4: ignore journal checksum on remount; don't fail
Jan Mrazek (1):
ext4: change to use setup_timer() instead of init_timer()
Omar Sandoval (1):
ext4: fix indirect punch hole corruption
Theodore Ts'o (1):
ext4: reserve codepoints used by the ext4 encryption feature
Xiaoguang Wang (1):
ext4: fix mmap data corruption in nodelalloc mode when blocksize < pagesize
fs/ext4/ext4.h | 18 ++++++++---
fs/ext4/indirect.c | 105 +++++++++++++++++++++++++++++++++++++++++--------------------
fs/ext4/inode.c | 7 +++++
fs/ext4/super.c | 31 ++++++++----------
fs/jbd2/recovery.c | 3 ++
5 files changed, 108 insertions(+), 56 deletions(-)
reply other threads:[~2015-02-22 23:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150222230104.GA16515@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).