diff options
| author | Michael Pratt <mpratt@google.com> | 2019-03-18 18:39:08 -0700 |
|---|---|---|
| committer | Shentubot <shentubot@google.com> | 2019-03-18 18:40:06 -0700 |
| commit | 8a499ae65f361fb01c2e4be03122f69910a8ba4a (patch) | |
| tree | 6b217045a189f94b9bd62756fe61bf40f34d622f /pkg/amutex/amutex_test.go | |
| parent | e420cc3e5d2066674d32d16ad885bee6b30da210 (diff) | |
Remove references to replaced child in Rename in ramfs/agentfs
In the case of a rename replacing an existing destination inode, ramfs
Rename failed to first remove the replaced inode. This caused:
1. A leak of a reference to the inode (making it live indefinitely).
2. For directories, a leak of the replaced directory's .. link to the
parent. This would cause the parent's link count to incorrectly
increase.
(2) is much simpler to test than (1), so that's what I've done.
agentfs has a similar bug with link count only, so the Dirent layer
informs the Inode if this is a replacing rename.
Fixes #133
PiperOrigin-RevId: 239105698
Change-Id: I4450af2462d8ae3339def812287213d2cbeebde0
Diffstat (limited to 'pkg/amutex/amutex_test.go')
0 files changed, 0 insertions, 0 deletions