From: Christoph Hellwig <hch@lst.de>
To: Tyler Hicks <code@tyhicks.com>
Cc: ecryptfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: cleanup truncate handling in ecryptfs v3
Date: Wed, 8 Apr 2026 08:06:35 +0200 [thread overview]
Message-ID: <20260408060719.714317-1-hch@lst.de> (raw)
Hi Tyler,
this series cleans up the truncate handling in ecryptfs. I did
it as preparation for some changes into size changing truncate
VFS interfaces I'm looking into in the moment. The changes have
passed the regression test suite in the userspace ecryptfs
repository and against the ecryptfs next branch.
Changes since v2:
- change the calling convention to only pass the upper ia to
__ecryptfs_truncate
Changes since v1:
- fix a pre-existing spelling error in a comment
- pass an explicit new_size argument to the main truncate routines
- fix a comment that kept obsolete information
Diffstat:
inode.c | 257 ++++++++++++++++++++++++++++------------------------------------
1 file changed, 115 insertions(+), 142 deletions(-)
next reply other threads:[~2026-04-08 6:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 6:06 Christoph Hellwig [this message]
2026-04-08 6:06 ` [PATCH 1/7] ecryptfs: cleanup ecryptfs_setattr Christoph Hellwig
2026-04-08 6:06 ` [PATCH 2/7] ecryptfs: streamline truncate_upper Christoph Hellwig
2026-04-09 0:07 ` Tyler Hicks
2026-04-08 6:06 ` [PATCH 3/7] ecryptfs: use ZERO_PAGE instead of allocating zeroed memory in truncate_upper Christoph Hellwig
2026-04-08 6:06 ` [PATCH 4/7] ecryptfs: combine the two ATTR_SIZE blocks in ecryptfs_setattr Christoph Hellwig
2026-04-08 6:06 ` [PATCH 5/7] ecryptfs: merge ecryptfs_inode_newsize_ok into truncate_upper Christoph Hellwig
2026-04-08 6:06 ` [PATCH 6/7] ecryptfs: factor out a ecryptfs_iattr_to_lower helper Christoph Hellwig
2026-04-08 6:06 ` [PATCH 7/7] ecryptfs: keep the lower iattr contained in truncate_upper Christoph Hellwig
2026-04-09 0:08 ` cleanup truncate handling in ecryptfs v3 Tyler Hicks
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=20260408060719.714317-1-hch@lst.de \
--to=hch@lst.de \
--cc=code@tyhicks.com \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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