Page MenuHomeFreeBSD
Differential D43816

VFS: update VOP_FSYNC() debug check to reflect actual locking policy
ClosedPublic
Actions

Authored by jah on Feb 10 2024, 4:35 PM.
Tags
None
Referenced Files
F107036417: D43816.id134098.diff
Thu, Jan 9, 7:57 AM
Unknown Object (File)
Nov 21 2024, 6:00 PM
Unknown Object (File)
Sep 29 2024, 2:43 AM
Unknown Object (File)
Sep 27 2024, 4:08 PM
Unknown Object (File)
Sep 16 2024, 12:44 PM
Unknown Object (File)
Sep 13 2024, 6:37 AM
Unknown Object (File)
Aug 30 2024, 11:02 AM
Unknown Object (File)
Aug 30 2024, 11:02 AM
View All 30 Files
Subscribers
imp

Details

Reviewers
kib
markj
olce
Commits
rGd0bb255d1fcb: VFS: update VOP_FSYNC() debug check to reflect actual locking policy
rG9530182e371d: VFS: update VOP_FSYNC() debug check to reflect actual locking policy
Summary

Shared vs. exclusive locking is determined not by MNT_EXTENDED_SHARED
but by MNT_SHARED_WRITES (although there are several places that
ignore this and simply always use an exclusive lock). Also add a
comment on the possible difference between VOP_GETWRITEMOUNT(vp)
and vp->v_mount on this path.

Found by local testing of unionfs atop ZFS with DEBUG_VFS_LOCKS.

MFC after: 2 weeks

Diff Detail

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

Revision Contents
Changeset List

PathSize
sys/
kern/
17 lines

Diff 134565

View Options

sys/kern/vfs_subr.c

Loading...