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 changes for 4.1-rc2
Date: Sun, 3 May 2015 21:21:32 -0400 [thread overview]
Message-ID: <20150504012132.GA31465@thunk.org> (raw)
The following changes since commit 6ddb2447846a8ece111e316a2863c2355023682d:
ext4 crypto: enable encryption feature flag (2015-04-16 01:56:00 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/for_linus_stable
for you to fetch changes up to 2c869b262a10ca99cb866d04087d75311587a30c:
ext4: fix growing of tiny filesystems (2015-05-02 23:58:32 -0400)
----------------------------------------------------------------
Some miscellaneous bug fixes and some final on-disk and ABI changes
for ext4 encryption which provide better security and performance.
----------------------------------------------------------------
Chanho Park (1):
ext4 crypto: remove duplicated encryption mode definitions
Davide Italiano (1):
ext4: move check under lock scope to close a race.
Herbert Xu (1):
ext4 crypto: do not select from EXT4_FS_ENCRYPTION
Jan Kara (1):
ext4: fix growing of tiny filesystems
Lukas Czerner (1):
ext4: fix data corruption caused by unwritten and delayed extents
Theodore Ts'o (2):
ext4 crypto: simplify and speed up filename encryption
ext4 crypto: add padding to filenames before encrypting
fs/ext4/Kconfig | 9 ++-
fs/ext4/crypto_fname.c | 280 +++++++++++++++++++++++++++++++++++++++------------------------------------
fs/ext4/crypto_key.c | 1 +
fs/ext4/crypto_policy.c | 14 ++--
fs/ext4/dir.c | 2 +-
fs/ext4/ext4.h | 16 ++---
fs/ext4/ext4_crypto.h | 11 ++-
fs/ext4/extents.c | 15 ++--
fs/ext4/extents_status.c | 8 +++
fs/ext4/inode.c | 2 +
fs/ext4/namei.c | 72 ++------------------
fs/ext4/resize.c | 7 +-
fs/ext4/symlink.c | 2 +-
13 files changed, 210 insertions(+), 229 deletions(-)
reply other threads:[~2015-05-04 1:21 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=20150504012132.GA31465@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).