src/sys/fs/tmpfs/tmpfs_vfsops.c, branch upstream/11.0.0

Check suspendability on the mountpoint returned by VOP_GETWRITEMOUNT.

2015-07-05T22:37:33Z

This obviates the need for a MNTK_SUSPENDABLE flag, since passthrough filesystems like nullfs and unionfs no longer need to inherit this information from their lower layer(s). This change also restores the pre-r273336 behaviour of using the presence of a susp_clean VFS method to request suspension support. Reviewed by: kib, mjg Differential Revision: https://reviews.freebsd.org/D2937

Update mtime for tmpfs files modified through memory mapping. Similar

2015-01-28T10:37:23Z

to UFS, perform updates during syncer scans, which in particular means that tmpfs now performs scan on sync. Also, this means that a mtime update may be delayed up to 30 seconds after the write. The vm_object' OBJ_TMPFS_DIRTY flag for tmpfs swap object is similar to the OBJ_MIGHTBEDIRTY flag for the vnode object, it indicates that object could have been dirtied. Adapt fast page fault handler and vm_object_set_writeable_dirty() to handle OBJ_TMPFS_NODE same as OBJT_VNODE. Reported by: Ronald Klop Tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 2 weeks

tmpfs does not use UVM on FreeBSD.

2015-01-28T10:25:35Z

Sponsored by: The FreeBSD Foundation MFC after: 3 days

tmpfs: allow shared file lookups

2014-10-21T21:27:13Z

Tested by: pho

Provide vfs suspension support only for filesystems which need it, take

2014-10-20T18:00:50Z

two. nullfs and unionfs need to request suspension if underlying filesystem(s) use it. Utilize mnt_kern_flag for this purpose. This is a fixup for 273271. No strong objections from: kib Pointy hat to: mjg MFC after: 2 weeks

Provide vfs suspension support only for filesystems which need it.

2014-10-19T06:59:33Z

Need is expressed by providing vfs_susp_clean function in vfsops. Differential Revision: D952 Reviewed by: kib (previous version) MFC after: 2 weeks

Rework the tmpfs unmount.

2014-07-14T09:52:33Z

- Suspend filesystem for unmount. This prevents new tmpfs nodes from instantiating, and also ensures that only unmount thread can destroy nodes. - Do not start tmpfs node deletion until all vnodes are reclaimed, which guarantees that no thread can access tmpfs data. For this, call vflush() in the loop, until the mnt_nvnodelistsize is non-zero. Note that after mnt_nvnodelistsize becomes 0, insmntque() blocks insertion of a vnode germ into the mount list of vnodes. - Fail node allocation when the filesystem is being unmounted. This is race-free due to the vflush() call in loop. This is mostly cosmetic, avoiding some more work which might be done until suspension in unmount is started. Note that there is currently no way to prevent new vnode instantiation from readers during the unmount. Due to this, forced unmount might live-lock if vflush() loop cannot get to the zero vnode count due to races with readers. The unmount would proceed after the load is lifted. Tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 2 weeks

Remove code separator lines which do not conform to style(9).

2014-07-14T08:17:11Z

Sponsored by: The FreeBSD Foundation MFC after: 2 weeks

Fix -o size less than PAGE_SIZE resulting in SIZE_MAX being used.

2014-03-14T01:43:55Z

Discussed with: kib MFC after: 2 weeks

Allow tmpfs be mounted inside jail.

2013-08-23T22:52:20Z