From: Tyler Hicks <code@tyhicks.com>
To: Christoph Hellwig <hch@lst.de>
Cc: ecryptfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 6/7] ecryptfs: merge ecryptfs_inode_newsize_ok into truncate_upper
Date: Mon, 6 Apr 2026 01:09:12 -0500 [thread overview]
Message-ID: <adNOCD5DvV7yaU_Z@yaupon> (raw)
In-Reply-To: <20260331153752.4049454-7-hch@lst.de>
On 2026-03-31 17:37:27, Christoph Hellwig wrote:
> Both callers of ecryptfs_inode_newsize_ok call truncate_upper right
> after. Merge ecryptfs_inode_newsize_ok into truncate_upper to simplify
> the logic.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
This one looks good to me.
Tyler
> ---
> fs/ecryptfs/inode.c | 53 +++++++++++++++------------------------------
> 1 file changed, 17 insertions(+), 36 deletions(-)
>
> diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c
> index a7dc25fae8ee..c87ee3c6ecba 100644
> --- a/fs/ecryptfs/inode.c
> +++ b/fs/ecryptfs/inode.c
> @@ -736,6 +736,23 @@ static int truncate_upper(struct dentry *dentry, struct iattr *lower_ia)
> return 0;
> }
>
> + crypt_stat = &ecryptfs_inode_to_private(inode)->crypt_stat;
> + lower_size_before_truncate =
> + upper_size_to_lower_size(crypt_stat, i_size);
> + lower_size_after_truncate =
> + upper_size_to_lower_size(crypt_stat, lower_ia->ia_size);
> + if (lower_size_after_truncate > lower_size_before_truncate) {
> + /*
> + * The eCryptfs inode and the new *lower* size are mixed here
> + * because we may not have the lower i_mutex held and/or it may
> + * not be appropriate to call inode_newsize_ok() with inodes
> + * from other filesystems.
> + */
> + rc = inode_newsize_ok(inode, lower_size_after_truncate);
> + if (rc)
> + return rc;
> + }
> +
> rc = ecryptfs_get_lower_file(dentry, inode);
> if (rc)
> return rc;
> @@ -754,7 +771,6 @@ static int truncate_upper(struct dentry *dentry, struct iattr *lower_ia)
> goto out;
> }
>
> - crypt_stat = &ecryptfs_inode_to_private(d_inode(dentry))->crypt_stat;
> if (!(crypt_stat->flags & ECRYPTFS_ENCRYPTED)) {
> truncate_setsize(inode, lower_ia->ia_size);
> goto out;
> @@ -787,42 +803,15 @@ static int truncate_upper(struct dentry *dentry, struct iattr *lower_ia)
> * We are reducing the size of the ecryptfs file, and need to know if we
> * need to reduce the size of the lower file.
> */
> - lower_size_before_truncate =
> - upper_size_to_lower_size(crypt_stat, i_size);
> - lower_size_after_truncate =
> - upper_size_to_lower_size(crypt_stat, lower_ia->ia_size);
> if (lower_size_after_truncate < lower_size_before_truncate)
> lower_ia->ia_size = lower_size_after_truncate;
> else
> lower_ia->ia_valid &= ~ATTR_SIZE;
> -
> out:
> ecryptfs_put_lower_file(inode);
> return rc;
> }
>
> -static int ecryptfs_inode_newsize_ok(struct inode *inode, loff_t offset)
> -{
> - struct ecryptfs_crypt_stat *crypt_stat;
> - loff_t lower_oldsize, lower_newsize;
> -
> - crypt_stat = &ecryptfs_inode_to_private(inode)->crypt_stat;
> - lower_oldsize = upper_size_to_lower_size(crypt_stat,
> - i_size_read(inode));
> - lower_newsize = upper_size_to_lower_size(crypt_stat, offset);
> - if (lower_newsize > lower_oldsize) {
> - /*
> - * The eCryptfs inode and the new *lower* size are mixed here
> - * because we may not have the lower i_mutex held and/or it may
> - * not be appropriate to call inode_newsize_ok() with inodes
> - * from other filesystems.
> - */
> - return inode_newsize_ok(inode, lower_newsize);
> - }
> -
> - return 0;
> -}
> -
> /**
> * ecryptfs_truncate
> * @dentry: The ecryptfs layer dentry
> @@ -841,10 +830,6 @@ int ecryptfs_truncate(struct dentry *dentry, loff_t new_length)
> };
> int rc;
>
> - rc = ecryptfs_inode_newsize_ok(d_inode(dentry), new_length);
> - if (rc)
> - return rc;
> -
> rc = truncate_upper(dentry, &lower_ia);
> if (!rc && lower_ia.ia_valid & ATTR_SIZE) {
> struct dentry *lower_dentry = ecryptfs_dentry_to_lower(dentry);
> @@ -936,10 +921,6 @@ static int ecryptfs_setattr(struct mnt_idmap *idmap,
> if (ia->ia_valid & ATTR_FILE)
> lower_ia.ia_file = ecryptfs_file_to_lower(ia->ia_file);
> if (ia->ia_valid & ATTR_SIZE) {
> - rc = ecryptfs_inode_newsize_ok(inode, ia->ia_size);
> - if (rc)
> - goto out;
> -
> rc = truncate_upper(dentry, &lower_ia);
> if (rc < 0)
> goto out;
> --
> 2.47.3
>
next prev parent reply other threads:[~2026-04-06 6:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 15:37 cleanup truncate handling in ecryptfs Christoph Hellwig
2026-03-31 15:37 ` [PATCH 1/7] ecryptfs: streamline truncate_upper Christoph Hellwig
2026-04-06 5:52 ` Tyler Hicks
2026-04-06 6:28 ` Christoph Hellwig
2026-03-31 15:37 ` [PATCH 2/7] ecryptfs: cleanup ecryptfs_setattr Christoph Hellwig
2026-04-06 5:52 ` Tyler Hicks
2026-03-31 15:37 ` [PATCH 3/7] ecryptfs: use ZERO_PAGE instead of allocating zeroed memory in truncate_upper Christoph Hellwig
2026-04-06 5:52 ` Tyler Hicks
2026-03-31 15:37 ` [PATCH 4/7] ecryptfs: combine the two ATTR_SIZE blocks in ecryptfs_setattr Christoph Hellwig
2026-04-06 5:53 ` Tyler Hicks
2026-03-31 15:37 ` [PATCH 5/7] ecryptfs: sanitize struct iattr handling in truncate_upper Christoph Hellwig
2026-04-06 5:58 ` Tyler Hicks
2026-04-06 6:22 ` Tyler Hicks
2026-04-06 6:27 ` Christoph Hellwig
2026-04-06 6:59 ` Tyler Hicks
2026-03-31 15:37 ` [PATCH 6/7] ecryptfs: merge ecryptfs_inode_newsize_ok into truncate_upper Christoph Hellwig
2026-04-06 6:09 ` Tyler Hicks [this message]
2026-03-31 15:37 ` [PATCH 7/7] ecryptfs: call notify_change from truncate_upper Christoph Hellwig
2026-04-06 6:52 ` Tyler Hicks
-- strict thread matches above, loose matches on Subject: below --
2026-04-07 14:02 cleanup truncate handling in ecryptfs v2 Christoph Hellwig
2026-04-07 14:02 ` [PATCH 6/7] ecryptfs: merge ecryptfs_inode_newsize_ok into truncate_upper Christoph Hellwig
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=adNOCD5DvV7yaU_Z@yaupon \
--to=code@tyhicks.com \
--cc=ecryptfs@vger.kernel.org \
--cc=hch@lst.de \
--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