mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tal Zussman <tz2294@columbia.edu>
To: Tyler Hicks <code@tyhicks.com>
Cc: ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>
Subject: Re: [PATCH 0/7] ecryptfs: remove the remaining struct page usage
Date: Thu, 22 Oct 2026 12:30:24 -0400	[thread overview]
Message-ID: <816dcdc4-7b4f-4d8a-982d-5fe45c3c3e99@columbia.edu> (raw)
In-Reply-To: <20261014-ecryptfs-folio-v1-0-f4412187b1d3@columbia.edu>

On 10/14/26 9:35 PM, Tal Zussman wrote:
> Convert the page cache side of the encryption path to folios, and use
> plain kernel memory for the buffers that were only pages because of the
> old interfaces: the ciphertext block, the header buffer from
> ecryptfs_get_zeroed_pages(), and the scatterlists built by
> virt_to_scatterlist(). Also make a shrinking truncate zero the tail of
> the last folio in place, as other filesystems do, instead of copying
> from the zero page through the write path. After this, fs/ecryptfs has
> no struct page usage left.
> 
> Ran cleanly with fsx and fsstress on ecryptfs over ext4 in the default,
> xattr, and passthrough mount options.
> 
> ---
> Tal Zussman (7):
>       ecryptfs: remove struct ecryptfs_page_crypt_context
>       ecryptfs: use a folio and a buffer in crypt_extent()
>       ecryptfs: use kzalloc() for the header buffer
>       ecryptfs: use sg_init_one() instead of virt_to_scatterlist()
>       ecryptfs: zero the tail of the last folio in place on truncate
>       ecryptfs: rename functions to refer to folios
>       ecryptfs: refer to folios in comments and printk strings
> 

Sashiko found some issues with patches 4 and 5. I'll send v2 with fixes
soon.

Thanks,
Tal


      parent reply	other threads:[~2026-10-22 16:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  1:35 Tal Zussman
2026-10-15  1:35 ` [PATCH 1/7] ecryptfs: remove struct ecryptfs_page_crypt_context Tal Zussman
2026-10-15  1:35 ` [PATCH 2/7] ecryptfs: use a folio and a buffer in crypt_extent() Tal Zussman
2026-10-15  1:35 ` [PATCH 3/7] ecryptfs: use kzalloc() for the header buffer Tal Zussman
2026-10-15  1:35 ` [PATCH 4/7] ecryptfs: use sg_init_one() instead of virt_to_scatterlist() Tal Zussman
2026-10-15  1:35 ` [PATCH 5/7] ecryptfs: zero the tail of the last folio in place on truncate Tal Zussman
2026-10-15  1:35 ` [PATCH 6/7] ecryptfs: rename functions to refer to folios Tal Zussman
2026-10-15  1:35 ` [PATCH 7/7] ecryptfs: refer to folios in comments and printk strings Tal Zussman
2026-10-22 16:30 ` Tal Zussman [this message]

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=816dcdc4-7b4f-4d8a-982d-5fe45c3c3e99@columbia.edu \
    --to=tz2294@columbia.edu \
    --cc=code@tyhicks.com \
    --cc=ecryptfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@infradead.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

all inboxes | Powered by JetHome®