[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <176679755972.16766.8394247113563710609@noble.neil.brown.name>
Date: Sat, 27 Dec 2025 12:05:59 +1100
From: NeilBrown <neilb@...mail.net>
To: "Tyler Hicks" <code@...icks.com>
Cc: "Christian Brauner" <brauner@...nel.org>,
"Jeff Layton" <jlayton@...nel.org>, "Amir Goldstein" <amir73il@...il.com>,
ecryptfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Fix two regressions from
start_creating()/start_removing() conversion
On Wed, 24 Dec 2025, Tyler Hicks wrote:
> When running the eCryptfs test suite on v6.19-rc2, I noticed BUG splats
> from every test and that the umount utility was segfaulting when tearing
> down after a test. Bisection led me to commit f046fbb4d81d ("ecryptfs:
> use new start_creating/start_removing APIs").
>
> This patch series addresses that regression and also a mknod problem
> spotted during code review.
>
> Tyler
>
> Tyler Hicks (2):
> ecryptfs: Fix improper mknod pairing of
> start_creating()/end_removing()
> ecryptfs: Release lower parent dentry after creating dir
>
> fs/ecryptfs/inode.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Thanks for finding and fixing these.
both
Reviewed-by: NeilBrown <neil@...wn.name>
I note that in https://lore.kernel.org/all/ZCuSLNnFQEdOHW0c@sequoia/ you
said of ecryptfs:
I'll send a patch to deprecate and mark for removal in 2025.
Did it ever get marked for removal? Is there a chance that it might be
removed?
Thanks,
NeilBrown
Powered by blists - more mailing lists