Page MenuHomeFreeBSD

tarfs: Correctly track link count.
ClosedPublic

Authored by des on Mar 10 2023, 5:50 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 30, 8:43 AM
Unknown Object (File)
Sun, Apr 26, 4:27 PM
Unknown Object (File)
Sun, Apr 26, 7:01 AM
Unknown Object (File)
Thu, Apr 23, 10:06 AM
Unknown Object (File)
Apr 8 2026, 2:09 AM
Unknown Object (File)
Apr 3 2026, 5:14 PM
Unknown Object (File)
Apr 2 2026, 11:39 PM
Unknown Object (File)
Mar 21 2026, 10:27 PM
Subscribers

Details

Summary

Sponsored by: Juniper Networks, Inc.
Sponsored by: Klara, Inc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

des requested review of this revision.Mar 10 2023, 5:50 PM

buggy, will resubmit

sys/fs/tarfs/tarfs_vfsops.c
745

What protects other->nlink during the increment? Could two calls to tarfs_alloc_one() executed in parallel, targeting the same dst node?

Or even, what protects other itself? For instance, could unmount occur in parallel with the tarfs_alloc_one()?

sys/fs/tarfs/tarfs_vfsops.c
745

tarfs_alloc_one() is called sequentially during mount, and tarfs_free_node() is called sequentially during unmount or while cleaning up after a failed mount.

This revision is now accepted and ready to land.Mar 13 2023, 5:56 PM
This revision was automatically updated to reflect the committed changes.