src-test/sys/security/lomac, branch mainFreeBSD source treehttps://cgit-dev.freebsd.org/src-test/atom?h=main2002-12-03T15:12:36ZUnhook the old LOMAC module, now replaced with mac_lomac.2002-12-03T15:12:36ZRobert Watsonrwatson@FreeBSD.org2002-12-03T15:12:36Zurn:sha1:c3a04e1ea4e87a7e7dad36db54db501427e6a366
Approved by: re (jhb)
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
Regularize the vop_stdlock'ing protocol across all the filesystems2002-10-14T03:20:36ZKirk McKusickmckusick@FreeBSD.org2002-10-14T03:20:36Zurn:sha1:a5b65058d5e43141777953576267ecf12476e715
that use it. Specifically, vop_stdlock uses the lock pointed to by
vp->v_vnlock. By default, getnewvnode sets up vp->v_vnlock to
reference vp->v_lock. Filesystems that wish to use the default
do not need to allocate a lock at the front of their node structure
(as some still did) or do a lockinit. They can simply start using
vn_lock/VOP_UNLOCK. Filesystems that wish to manage their own locks,
but still use the vop_stdlock functions (such as nullfs) can simply
replace vp->v_vnlock with a pointer to the lock that they wish to
have used for the vnode. Such filesystems are responsible for
setting the vp->v_vnlock back to the default in their vop_reclaim
routine (e.g., vp->v_vnlock = &vp->v_lock).
In theory, this set of changes cleans up the existing filesystem
lock interface and should have no function change to the existing
locking scheme.
Sponsored by: DARPA & NAI Labs.
- Use vrefcnt() instead of v_usecount.2002-09-25T02:42:43ZJeff Robersonjeff@FreeBSD.org2002-09-25T02:42:43Zurn:sha1:37ab0e0d814e4b071d6f602b58556380d091f4b1Remove all use of vnode->v_tag, replacing with appropriate substitutes.2002-09-14T09:02:28ZNate Lawsonnjl@FreeBSD.org2002-09-14T09:02:28Zurn:sha1:06be2aaa8320ba839a837d20e35f35c3efdf7587
v_tag is now const char * and should only be used for debugging.
Additionally:
1. All users of VT_NTS now check vfsconf->vf_type VFCF_NETWORK
2. The user of VT_PROCFS now checks for the new flag VV_PROCDEP, which
is propagated by pseudofs to all child vnodes if the fs sets PFS_PROCDEP.
Suggested by: phk
Reviewed by: bde, rwatson (earlier version)
Keep a copy of the credential used to mount filesystems around so2002-08-19T06:52:21ZPoul-Henning Kampphk@FreeBSD.org2002-08-19T06:52:21Zurn:sha1:fee7d450d8874cf822cdfa62a1e1a7c9c4f7f47b
we can check and use it later on.
Change the pieces of code which relied on mount->mnt_stat.f_owner
to check which user mounted the filesystem.
This became needed as the EA code needs to be able to allocate
blocks for "system" EA users like ACLs.
There seems to be some half-baked (probably only quarter- actually)
notion that the superuser for a given filesystem is the user who
mounted it, but this has far from been carried through. It is
unclear if it should be.
Sponsored by: DARPA & NAI Labs.
- Replace v_flag with v_iflag and v_vflag2002-08-04T10:29:36ZJeff Robersonjeff@FreeBSD.org2002-08-04T10:29:36Zurn:sha1:e6e370a7fe930e04cec38bcc2e06be127ed7ee02
- v_vflag is protected by the vnode lock and is used when synchronization
with VOP calls is needed.
- v_iflag is protected by interlock and is used for dealing with vnode
management issues. These flags include X/O LOCK, FREE, DOOMED, etc.
- All accesses to v_iflag and v_vflag have either been locked or marked with
mp_fixme's.
- Many ASSERT_VOP_LOCKED calls have been added where the locking was not
clear.
- Many functions in vfs_subr.c were restructured to provide for stronger
locking.
Idea stolen from: BSD/OS
Get rid of warnings, there's no need to do preprocessor concatination of2002-06-01T18:45:33ZAlfred Perlsteinalfred@FreeBSD.org2002-06-01T18:45:33Zurn:sha1:5e8176f9cbca51245cb778135c6360dffbec0cd9
things with commas and equal signs.
Back out my lats commit of locking down a socket, it conflicts with hsu's work.2002-05-31T11:52:35ZSeigo Tanimuratanimura@FreeBSD.org2002-05-31T11:52:35Zurn:sha1:4cc20ab1f0f3d1126126327aa298ab88c974c53d
Requested by: hsu
Check for defined(__i386__) instead of just defined(i386) since the compiler2002-05-30T07:32:58ZAlfred Perlsteinalfred@FreeBSD.org2002-05-30T07:32:58Zurn:sha1:99b9331a4f693e66f880734cd446190fcf14508d
will be updated to only define(__i386__) for ANSI cleanliness.
Lock down a socket, milestone 1.2002-05-20T05:41:09ZSeigo Tanimuratanimura@FreeBSD.org2002-05-20T05:41:09Zurn:sha1:243917fe3b5e36464ab72473e872da9acd44aa1c
o Add a mutex (sb_mtx) to struct sockbuf. This protects the data in a
socket buffer. The mutex in the receive buffer also protects the data
in struct socket.
o Determine the lock strategy for each members in struct socket.
o Lock down the following members:
- so_count
- so_options
- so_linger
- so_state
o Remove *_locked() socket APIs. Make the following socket APIs
touching the members above now require a locked socket:
- sodisconnect()
- soisconnected()
- soisconnecting()
- soisdisconnected()
- soisdisconnecting()
- sofree()
- soref()
- sorele()
- sorwakeup()
- sotryfree()
- sowakeup()
- sowwakeup()
Reviewed by: alfred