From: "Theodore Ts'o" <tytso@mit.edu>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Matthew Wilcox <willy@infradead.org>,
Arnd Bergmann <arnd@kernel.org>, Tyler Hicks <code@tyhicks.com>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ecryptfs is unmaintained and untested
Date: Mon, 28 Oct 2024 21:33:28 -0700 [thread overview]
Message-ID: <20241029043328.GB3213@mit.edu> (raw)
In-Reply-To: <ef98d985-6153-416d-9d5e-9a8a8595461a@app.fastmail.com>
On Mon, Oct 28, 2024 at 09:50:37PM +0000, Arnd Bergmann wrote:
> On Mon, Oct 28, 2024, at 15:02, Matthew Wilcox wrote:
> >
> > This comment has been there since June 2021, so I think we can just
> > delete ecryptfs now?
>
> I have no opinion on removing ecryptfs, but I don't how possibly
> removing it is related to the patch I sent, as far as I can tell
> it just means it relies on both CONFIG_BLOCK and CONFIG_BUFFER_HEAD
> then.
>
> Is there any indication that the last users that had files on
> ecryptfs are unable to update their kernels?
Debian is still shipping ecryptfs-utils and is building and including
the ecryptfs kernel module in their distro kernel.`
So it seems likely that there are probably a non-zero (although
probably relatively small) number of ecryptfs users out there.
- Ted
next prev parent reply other threads:[~2024-10-30 20:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 14:18 [PATCH] eccryptfs: select CONFIG_BUFFER_HEAD Arnd Bergmann
2024-10-28 15:02 ` ecryptfs is unmaintained and untested Matthew Wilcox
2024-10-28 21:50 ` Arnd Bergmann
2024-10-29 4:33 ` Theodore Ts'o [this message]
2024-10-30 21:06 ` Tyler Hicks
2026-02-16 11:53 ` René Herman
2025-10-14 6:07 ` John Stultz
2025-10-14 14:39 ` Theodore Ts'o
2025-10-14 16:38 ` John Stultz
2025-10-14 16:54 ` Martin Steigerwald
2025-10-14 17:52 ` Theodore Ts'o
2025-10-14 16:52 ` Martin Steigerwald
2025-10-14 20:35 ` Eric Biggers
2025-10-15 1:31 ` Theodore Ts'o
2025-10-15 2:23 ` Eric Biggers
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=20241029043328.GB3213@mit.edu \
--to=tytso@mit.edu \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=code@tyhicks.com \
--cc=damien.lemoal@opensource.wdc.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