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 fixes for 7.0-rc1
Date: Wed, 18 Feb 2026 19:05:10 -0600 [thread overview]
Message-ID: <aZZhxvVTFRpbVNv2@yaupon> (raw)
Hi Linus,
This is the first pull request that I've sent to you in some time.
Christian has been picking up sporadic eCryptfs bug fixes, support for
new VFS hooks/functionality, etc., (thanks again!) but I have
time/interest to get more involved and received Christian's blessing.
This pull request consists of some really minor typo fixes that fell
through the cracks and some more recent code cleanups.
I've dusted off my notes on creating pull requests and think I got
everything correct but let me know if anything looks off.
The following changes since commit 9448598b22c50c8a5bb77a9103e2d49f134c9578:
Linux 6.19-rc2 (2025-12-21 15:52:04 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-7.0-rc1-fixes
for you to fetch changes up to 99853d9daef240a45e161d0e33487cda4810b999:
ecryptfs: Replace memcpy + NUL termination in ecryptfs_copy_filename (2026-01-12 20:21:27 -0600)
----------------------------------------------------------------
eCryptfs fixes for 7.0-rc1
The set of eCryptfs patches for the 7.0-rc1 merge window consists of
cleanups that are not intended to have any functional changes:
- Comment typo fixes
- Removal of an unused function declaration
- Use strscpy() instead of the deprecated strcpy()
- Use string copying helpers instead of memcpy() and manually
terminating strings
The patches have all spent time in linux-next and they do not regress
the tests in the ecryptfs-utils tree.
Signed-off-by: Tyler Hicks <code@tyhicks.com>
----------------------------------------------------------------
Baolin Liu (1):
ecryptfs: simplify list initialization in ecryptfs_parse_packet_set()
Slark Xiao (1):
ecryptfs: keystore: Fix typo 'the the' in comment
Thorsten Blum (7):
ecryptfs: Fix packet format comment in parse_tag_67_packet()
ecryptfs: Replace strcpy with strscpy in ecryptfs_set_default_crypt_stat_vals
ecryptfs: Replace strcpy with strscpy in ecryptfs_cipher_code_to_string
ecryptfs: Replace strcpy with strscpy in ecryptfs_validate_options
ecryptfs: Replace memcpy + NUL termination in ecryptfs_new_file_context
ecryptfs: Drop redundant NUL terminations after calling ecryptfs_to_hex
ecryptfs: Replace memcpy + NUL termination in ecryptfs_copy_filename
Zhang Zekun (1):
ecryptfs: Remove unused declartion ecryptfs_fill_zeros()
Zipeng Zhang (1):
ecryptfs: comment typo fix
fs/ecryptfs/crypto.c | 38 +++++++++++++-------------------------
fs/ecryptfs/debug.c | 1 -
fs/ecryptfs/ecryptfs_kernel.h | 3 +--
fs/ecryptfs/keystore.c | 19 ++++++++++---------
fs/ecryptfs/main.c | 9 +++++----
5 files changed, 29 insertions(+), 41 deletions(-)
next reply other threads:[~2026-02-19 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 1:05 Tyler Hicks [this message]
2026-02-21 1:20 ` [GIT PULL] eCryptfs fixes for 7.0-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=aZZhxvVTFRpbVNv2@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