Page MenuHomeFreeBSD

unionfs: implement VOP_UNP_* and remove special VSOCK vnode handling
ClosedPublic

Authored by jah on Mar 10 2024, 2:09 AM.
Tags
None
Referenced Files
F110743469: D44288.id135823.diff
Sat, Feb 22, 1:51 PM
F110742807: D44288.id135574.diff
Sat, Feb 22, 1:44 PM
Unknown Object (File)
Jan 11 2025, 12:00 PM
Unknown Object (File)
Jan 4 2025, 9:16 PM
Unknown Object (File)
Dec 23 2024, 3:53 PM
Unknown Object (File)
Dec 21 2024, 5:24 PM
Unknown Object (File)
Nov 17 2024, 3:07 PM
Unknown Object (File)
Nov 16 2024, 6:44 AM

Details

Summary

unionfs has a bunch of clunky special-case code to avoid creating
unionfs wrapper vnodes for AF_UNIX sockets. This was added in 2008
to address PR 118346, but in the intervening years the VOP_UNP_*
operations have been added to provide a clean interface to allow
sockets to work in the presence of stacked filesystems.

PR: 275871
Tested by: Karlo Miličević <karlo98.m@gmail.com>
MFC after: 2 weeks

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 56524
Build 53412: arc lint + arc unit

Event Timeline

jah requested review of this revision.Mar 10 2024, 2:09 AM
This revision is now accepted and ready to land.Mar 10 2024, 5:32 PM

Great! More cruft removed, including one call to unionfs_relookup(). I have a few suggestions.

sys/fs/unionfs/union_vnops.c
1044–1045

I would now assert that a_vp is also a unionfs node.

1067–1068

unp is never supposed to be NULL now here.

1070–1071

Same here.

Code review feedback, also remove a nonsensical check from unionfs_link()

This revision now requires review to proceed.Mar 16 2024, 3:49 PM
This revision is now accepted and ready to land.Mar 20 2024, 4:02 AM