linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Theodore Y. Ts'o" <tytso@mit.edu>,
	Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [GIT PULL] fscrypt updates for v5.3
Date: Mon, 8 Jul 2019 08:53:33 -0700	[thread overview]
Message-ID: <20190708155333.GA722@sol.localdomain> (raw)

The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07:

  Linux 5.2-rc2 (2019-05-26 16:49:19 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fscrypt-for-linus

for you to fetch changes up to 0564336329f0b03a78221ddf51e52af3665e5720:

  fscrypt: document testing with xfstests (2019-06-27 10:29:46 -0700)

----------------------------------------------------------------
fscrypt updates for v5.3

- Preparations for supporting encryption on ext4 filesystems where the
  filesystem block size is smaller than PAGE_SIZE.

- Don't allow setting encryption policies on dead directories.

- Various cleanups.

----------------------------------------------------------------
Chandan Rajendra (3):
      ext4: clear BH_Uptodate flag on decryption error
      ext4: decrypt only the needed blocks in ext4_block_write_begin()
      ext4: decrypt only the needed block in __ext4_block_zero_page_range()

Eric Biggers (14):
      fscrypt: simplify bounce page handling
      fscrypt: remove the "write" part of struct fscrypt_ctx
      fscrypt: rename fscrypt_do_page_crypto() to fscrypt_crypt_block()
      fscrypt: clean up some BUG_ON()s in block encryption/decryption
      fscrypt: introduce fscrypt_encrypt_block_inplace()
      fscrypt: support encrypting multiple filesystem blocks per page
      fscrypt: handle blocksize < PAGE_SIZE in fscrypt_zeroout_range()
      fscrypt: introduce fscrypt_decrypt_block_inplace()
      fscrypt: support decrypting multiple filesystem blocks per page
      fscrypt: decrypt only the needed blocks in __fscrypt_decrypt_bio()
      ext4: encrypt only up to last block in ext4_bio_write_page()
      fscrypt: remove unnecessary includes of ratelimit.h
      fscrypt: remove selection of CONFIG_CRYPTO_SHA256
      fscrypt: document testing with xfstests

Hongjie Fang (1):
      fscrypt: don't set policy for a dead directory

 Documentation/filesystems/fscrypt.rst |  43 ++++-
 fs/crypto/Kconfig                     |   1 -
 fs/crypto/bio.c                       |  73 +++------
 fs/crypto/crypto.c                    | 299 +++++++++++++++++++---------------
 fs/crypto/fname.c                     |   1 -
 fs/crypto/fscrypt_private.h           |  15 +-
 fs/crypto/hooks.c                     |   1 -
 fs/crypto/keyinfo.c                   |   1 -
 fs/crypto/policy.c                    |   2 +
 fs/ext4/inode.c                       |  37 +++--
 fs/ext4/page-io.c                     |  44 +++--
 fs/f2fs/data.c                        |  17 +-
 fs/ubifs/crypto.c                     |  19 ++-
 include/linux/fscrypt.h               |  96 +++++++----
 14 files changed, 363 insertions(+), 286 deletions(-)

             reply	other threads:[~2019-07-08 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 15:53 Eric Biggers [this message]
2019-07-11  4:40 ` [GIT PULL] fscrypt updates for v5.3 pr-tracker-bot

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=20190708155333.GA722@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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).