From: "Theodore Ts'o" <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-fscrypt@vger.kernel.org
Subject: [GIT PULL] fscrypt updates for 5.2
Date: Tue, 7 May 2019 19:30:42 -0400 [thread overview]
Message-ID: <20190507233042.GA28476@mit.edu> (raw)
The following changes since commit dc4060a5dc2557e6b5aa813bf5b73677299d62d2:
Linux 5.1-rc5 (2019-04-14 15:17:41 -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 2c58d548f5706d085c4b009f6abb945220460632:
fscrypt: cache decrypted symlink target in ->i_link (2019-04-17 12:43:29 -0400)
----------------------------------------------------------------
Clean up fscrypt's dcache revalidation support, and other
miscellaneous cleanups.
----------------------------------------------------------------
Eric Biggers (10):
fscrypt: drop inode argument from fscrypt_get_ctx()
fscrypt: remove WARN_ON_ONCE() when decryption fails
fscrypt: use READ_ONCE() to access ->i_crypt_info
fscrypt: clean up and improve dentry revalidation
fscrypt: fix race allowing rename() and link() of ciphertext dentries
fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
fscrypt: only set dentry_operations on ciphertext dentries
fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext
vfs: use READ_ONCE() to access ->i_link
fscrypt: cache decrypted symlink target in ->i_link
fs/crypto/bio.c | 8 +++-----
fs/crypto/crypto.c | 74 ++++++++++++++++++++++++++++++++++-------------------------------------
fs/crypto/fname.c | 5 +++--
fs/crypto/hooks.c | 68 +++++++++++++++++++++++++++++++++++++++++++++++++----------------
fs/crypto/keyinfo.c | 25 ++++++++++++++++++++++--
fs/crypto/policy.c | 6 +++---
fs/dcache.c | 2 ++
fs/ext4/ext4.h | 62 ++++++++++++++++++++++++++++++++++++++++++++---------------
fs/ext4/namei.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------
fs/ext4/readpage.c | 2 +-
fs/ext4/super.c | 3 +++
fs/f2fs/namei.c | 17 ++++++++++-------
fs/f2fs/super.c | 3 +++
fs/namei.c | 4 ++--
fs/ubifs/dir.c | 8 +++-----
fs/ubifs/super.c | 3 +++
include/linux/dcache.h | 2 +-
include/linux/fscrypt.h | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++---------------------
18 files changed, 298 insertions(+), 144 deletions(-)
next reply other threads:[~2019-05-07 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 23:30 Theodore Ts'o [this message]
2019-05-08 1:19 ` [GIT PULL] fscrypt updates for 5.2 Eric Biggers
2019-05-08 4:55 ` 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=20190507233042.GA28476@mit.edu \
--to=tytso@mit.edu \
--cc=linux-fscrypt@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