linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tyler Hicks <code@tyhicks.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: [GIT PULL] eCryptfs updates for 5.13-rc1
Date: Wed, 5 May 2021 21:28:51 -0500	[thread overview]
Message-ID: <20210506022851.GA622556@elm> (raw)

Hi Linus,

The following changes since commit d434405aaab7d0ebc516b68a8fc4100922d7f5ef:

  Linux 5.12-rc7 (2021-04-11 15:16:13 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-5.13-rc1-updates

for you to fetch changes up to 9046625511ad8dfbc8c6c2de16b3532c43d68d48:

  ecryptfs: fix kernel panic with null dev_name (2021-04-19 05:50:32 +0000)

Note that there's a "back merge" in here because I forgot to send out a
5.12 PR for two small cleanups that were queued up so my branch was
still on a 5.11-rc release. I did the back merge because the W=1 fixes
needed the idmapped mounts changes that landed in 5.12 and I had hoped
to merge (but didn't) some additional changes to switch over to using a
private clone of the lower mount, which also relied on the idmapped
mounts changes. I won't make a habit out of back merging but wanted to
mention the reasoning since this is the first time I've felt I needed to
do it. Please let me know if it is a problem.

----------------------------------------------------------------
Code cleanups and a bug fix
- W=1 compiler warning cleanups
- Mutex initialization simplification
- Protect against NULL pointer exception during mount

----------------------------------------------------------------
Christian Brauner (1):
      ecryptfs: remove unused helpers

Jeffrey Mitchell (1):
      ecryptfs: fix kernel panic with null dev_name

Lee Jones (13):
      ecryptfs: read_write: File headers do not make good candidates for kernel-doc
      ecryptfs: debug: Demote a couple of kernel-doc abuses
      ecryptfs: dentry: File headers are not good candidates for kernel-doc
      ecryptfs: kthread: Demote file header and provide description for 'cred'
      ecryptfs: file: Demote kernel-doc abuses
      ecryptfs: super: Fix formatting, naming and kernel-doc abuses
      ecryptfs: messaging: Add missing param descriptions and demote abuses
      ecryptfs: main: Demote a bunch of non-conformant kernel-doc headers
      ecryptfs: miscdev: File headers are not good kernel-doc candidates
      ecryptfs: crypto: Supply some missing param descriptions and demote abuses
      ecryptfs: mmap: Help out one function header and demote other abuses
      ecryptfs: inode: Help out nearly-there header and demote non-conformant ones
      ecryptfs: keystore: Fix some kernel-doc issues and demote non-conformant headers

Sascha Hauer (1):
      ecryptfs: Fix typo in message

Tom Rix (1):
      eCryptfs: add a semicolon

Tyler Hicks (1):
      Merge tag 'v5.12-rc7' into ecryptfs/next

Ye Bin (1):
      eCryptfs: Use DEFINE_MUTEX() for mutex lock

Zheng Yongjun (1):
      ecryptfs: use DEFINE_MUTEX() for mutex lock

 fs/ecryptfs/crypto.c          | 25 ++++++++++++-------------
 fs/ecryptfs/debug.c           |  4 ++--
 fs/ecryptfs/dentry.c          |  2 +-
 fs/ecryptfs/ecryptfs_kernel.h | 14 +-------------
 fs/ecryptfs/file.c            |  4 ++--
 fs/ecryptfs/inode.c           | 11 +++++------
 fs/ecryptfs/keystore.c        | 15 ++++++++-------
 fs/ecryptfs/kthread.c         |  3 ++-
 fs/ecryptfs/main.c            | 30 ++++++++++++++++++------------
 fs/ecryptfs/messaging.c       | 14 +++++++-------
 fs/ecryptfs/miscdev.c         |  3 ++-
 fs/ecryptfs/mmap.c            | 11 ++++++-----
 fs/ecryptfs/read_write.c      |  4 +++-
 fs/ecryptfs/super.c           |  8 ++++----
 14 files changed, 73 insertions(+), 75 deletions(-)

             reply	other threads:[~2021-05-06  2:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  2:28 Tyler Hicks [this message]
2021-05-06 17:57 ` [GIT PULL] eCryptfs updates for 5.13-rc1 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=20210506022851.GA622556@elm \
    --to=code@tyhicks.com \
    --cc=akpm@linux-foundation.org \
    --cc=ecryptfs@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).