EcryptFS development
 help / color / mirror / Atom feed
From: Tyler Hicks <code@tyhicks.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-kernel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: [GIT PULL] eCryptfs updates for 7.2-rc1
Date: Thu, 25 Jun 2026 21:54:42 -0500	[thread overview]
Message-ID: <aj3p8nYWZPTbkUWW@yaupon> (raw)

Hi Linus,

The following changes since commit 5d6919055dec134de3c40167a490f33c74c12581:

  Linux 7.1-rc3 (2026-05-10 14:08:09 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 95ce5ffd54cf66098f91892f98606c3bd33846fe:

  ecryptfs: use kasprintf in ecryptfs_crypto_api_algify_cipher_name (2026-06-04 14:15:08 -0500)

----------------------------------------------------------------
The set of eCryptfs changes for the 7.2-rc1 merge window consists of:
- Code cleanup to replace kmalloc()/snprintf() with kasprintf()
- Code cleanup to simplify code flow by removing an unnecessary variable

There should be no functional changes. The patches have all spent time
in linux-next and they pass all tests in the ecryptfs-utils tree.

----------------------------------------------------------------
Alexey Velichayshiy (1):
      ecryptfs: remove redundant variable found_auth_tok

Thorsten Blum (1):
      ecryptfs: use kasprintf in ecryptfs_crypto_api_algify_cipher_name

 fs/ecryptfs/crypto.c   | 24 +++++++-----------------
 fs/ecryptfs/keystore.c | 16 +++++-----------
 2 files changed, 12 insertions(+), 28 deletions(-)

             reply	other threads:[~2026-06-26  2:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  2:54 Tyler Hicks [this message]
2026-06-26 15:45 ` [GIT PULL] eCryptfs updates for 7.2-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=aj3p8nYWZPTbkUWW@yaupon \
    --to=code@tyhicks.com \
    --cc=brauner@kernel.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