src-test2/sys/kern/vnode_if.src, branch stable/4 FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=stable%2F4 2001-05-18T09:58:52Z MFC: introduce VOP_CREATEVOBJECT(), VOP_GETVOBJECT and VOP_DESTROYVOBJECT() 2001-05-18T09:58:52Z Boris Popov bp@FreeBSD.org 2001-05-18T09:58:52Z urn:sha1:f69b6a90193c71701ea2bb3ef1c37dfabe75cc2c which help to get proper reference to VM backing object. MFC: sync kq up to current (extend to device layer, plus other fixes) 2001-02-26T04:23:21Z Jonathan Lemon jlemon@FreeBSD.org 2001-02-26T04:23:21Z urn:sha1:d2180fd16490150b692c1f687ae68f4eea73e83a o MFC locking changes in extended attribute interface (locks required on vnodes 2000-07-28T18:46:49Z Robert Watson rwatson@FreeBSD.org 2000-07-28T18:46:49Z urn:sha1:b8b69075d297f226e53b1c0d2df15a385f9a4c34 for all extended attribute vnops) o MFC related formatting changes to decrease diffs between -current and -stable in that code. Obtained from: TrustedBSD Project Second pass commit to introduce new ACL and Extended Attribute system 1999-12-19T06:08:07Z Robert Watson rwatson@FreeBSD.org 1999-12-19T06:08:07Z urn:sha1:91f37dcba1648b1f24e2913c3ab78fc4eae35991 calls, vnops, vfsops, both in /kern, and to individual file systems that require a vfsop_ array entry. Reviewed by: eivind Since VOP_LOCK can be used to up and downgrade locks, it is not possible 1999-12-18T23:01:52Z Eivind Eklund eivind@FreeBSD.org 1999-12-18T23:01:52Z urn:sha1:d776d82c4d1f366d4288025fc627b09675013381 to say anything about the lockstate before and after it. Thus, change the lockspec from U L U to ? ? ?. Introduce NDFREE (and remove VOP_ABORTOP) 1999-12-15T23:02:35Z Eivind Eklund eivind@FreeBSD.org 1999-12-15T23:02:35Z urn:sha1:762e6b856c64ee48f286a7f0b45d0067e556b252 Lock reporting and assertion changes. 1999-12-11T16:13:02Z Eivind Eklund eivind@FreeBSD.org 1999-12-11T16:13:02Z urn:sha1:6bdfe06ad9337a33a402bc933006265c30980780 * lockstatus() and VOP_ISLOCKED() gets a new process argument and a new return value: LK_EXCLOTHER, when the lock is held exclusively by another process. * The ASSERT_VOP_(UN)LOCKED family is extended to use what this gives them * Extend the vnode_if.src format to allow more exact specification than locked/unlocked. This commit should not do any semantic changes unless you are using DEBUG_VFS_LOCKS. Discussed with: grog, mch, peter, phk Reviewed by: peter Remove WILLRELE from VOP_SYMLINK 1999-11-13T20:58:17Z Eivind Eklund eivind@FreeBSD.org 1999-11-13T20:58:17Z urn:sha1:dd8c04f4c7b9354c57ae38ef2822d7ae408c6a62 Note: Previous commit to these files (except coda_vnops and devfs_vnops) that claimed to remove WILLRELE from VOP_RENAME actually removed it from VOP_MKNOD. Remove WILLRELE from VOP_RENAME 1999-11-12T03:34:28Z Eivind Eklund eivind@FreeBSD.org 1999-11-12T03:34:28Z urn:sha1:edfe736df916f9ca24d812ba13c52aed1fe8b4da Move the vop_islocked declaration to the top, in preparation for committing 1999-09-26T18:10:59Z Eivind Eklund eivind@FreeBSD.org 1999-09-26T18:10:59Z urn:sha1:5c69e12c0e24698d75fa84ce448bbcd3d97fa78b code to auto-generate assertions from the lockspecs