From: Tyler Hicks <code@tyhicks.com>
To: NeilBrown <neil@brown.name>,
Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
Amir Goldstein <amir73il@gmail.com>
Cc: ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Fix two regressions from start_creating()/start_removing() conversion
Date: Tue, 23 Dec 2025 13:41:51 -0600 [thread overview]
Message-ID: <20251223194153.2818445-1-code@tyhicks.com> (raw)
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(-)
base-commit: 9448598b22c50c8a5bb77a9103e2d49f134c9578
--
2.43.0
next reply other threads:[~2025-12-23 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 19:41 Tyler Hicks [this message]
2025-12-23 19:41 ` [PATCH 1/2] ecryptfs: Fix improper mknod pairing of start_creating()/end_removing() Tyler Hicks
2025-12-24 6:23 ` Amir Goldstein
2025-12-23 19:41 ` [PATCH 2/2] ecryptfs: Release lower parent dentry after creating dir Tyler Hicks
2025-12-24 6:37 ` Amir Goldstein
2025-12-24 6:31 ` [PATCH 0/2] Fix two regressions from start_creating()/start_removing() conversion Amir Goldstein
2025-12-24 14:47 ` Tyler Hicks
2025-12-24 12:58 ` Christian Brauner
2025-12-27 1:05 ` NeilBrown
2025-12-27 18:15 ` Amir Goldstein
2025-12-30 3:30 ` 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=20251223194153.2818445-1-code@tyhicks.com \
--to=code@tyhicks.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.