summaryrefslogtreecommitdiffstats
path: root/sys/xdr
diff options
context:
space:
mode:
authorkib <kib@FreeBSD.org>2014-07-14 09:30:37 +0000
committerkib <kib@FreeBSD.org>2014-07-14 09:30:37 +0000
commit8664d64bc36b1c178711d560358193de021c363b (patch)
tree81662c710560697ae0f6f033972aa0c2eec3adaf /sys/xdr
parente152d896521719791fa35fa048ca142de1bb5744 (diff)
downloadFreeBSD-src-8664d64bc36b1c178711d560358193de021c363b.zip
FreeBSD-src-8664d64bc36b1c178711d560358193de021c363b.tar.gz
The OBJ_TMPFS flag of vm_object means that there is unreclaimed tmpfs
vnode for the tmpfs node owning this object. The flag is currently used for two purposes. First, it allows to correctly handle VV_TEXT for tmpfs vnode when the ref count on the object is decremented to 1, similar to vnode_pager_dealloc() for regular filesystems. Second, it prevents some operations, which are done on OBJT_SWAP vm objects backing user anonymous memory, but are incorrect for the object owned by tmpfs node. The second kind of use of the OBJ_TMPFS flag is incorrect, since the vnode might be reclaimed, which clears the flag, but vm object operations must still be disallowed. Introduce one more flag, OBJ_TMPFS_NODE, which is permanently set on the object for VREG tmpfs node, and used instead of OBJ_TMPFS to test whether vm object collapse and similar actions should be disabled. Tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 2 weeks
Diffstat (limited to 'sys/xdr')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud