linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Tyler Hicks <code@tyhicks.com>
Subject: [git pull] ecryptfs series
Date: Sun, 2 May 2021 01:22:50 +0000	[thread overview]
Message-ID: <YI3+6jfW+mEMgx3x@zeniv-ca.linux.org.uk> (raw)

	The interesting part here is (ecryptfs) lock_parent() fixes -
its treatment of ->d_parent had been very wrong.  The rest is trivial
cleanups.

The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:

  Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.ecryptfs

for you to fetch changes up to 9d786beb6fe5cf8fcc1ce5336a89401eaa444fb6:

  ecryptfs: ecryptfs_dentry_info->crypt_stat is never used (2021-03-20 17:46:44 -0400)

----------------------------------------------------------------
Al Viro (4):
      ecryptfs: get rid of pointless dget/dput in ->symlink() and ->link()
      ecryptfs: saner API for lock_parent()
      ecryptfs: get rid of unused accessors
      ecryptfs: ecryptfs_dentry_info->crypt_stat is never used

 fs/ecryptfs/ecryptfs_kernel.h |  17 +----
 fs/ecryptfs/inode.c           | 163 +++++++++++++++++++-----------------------
 2 files changed, 75 insertions(+), 105 deletions(-)

             reply	other threads:[~2021-05-02  1:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02  1:22 Al Viro [this message]
2021-05-02 18:32 ` [git pull] ecryptfs series 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=YI3+6jfW+mEMgx3x@zeniv-ca.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=code@tyhicks.com \
    --cc=linux-fsdevel@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).