Fix two regressions from start_creating()/start_removing() conversion
Status from this message: Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | ecryptfs: Fix improper mknod pairing of start_creating()/end_removing()fs/ | +1 | 1 reply | |
| 2/2 | ecryptfs: Release lower parent dentry after creating dirfs/ | +1 | 1 reply |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Amir Goldstein | NeilBrown |
|---|---|---|
| Series | R-b | |
| 1/2 | R-b | |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] Fix two regressions from start_creating()/start_removing() conversion
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
Signature · 1 line
2.43.0