| commit | fa4a12c408e7819a51670d15087aadbf10659890 | |
| author | Matthew Dillon <dillon@apollo.backplane.com> | |
| Wed, 14 Feb 2018 07:02:18 +0000 (13 23:02 -0800) | ||
| committer | Matthew Dillon <dillon@apollo.backplane.com> | |
| Wed, 14 Feb 2018 07:02:18 +0000 (13 23:02 -0800) | ||
| tree | 04ea843a1cb0e50c04053aa2ee9f943262fd6e83 | treesnapshot (tar.gz zip) |
| parent | 6f5aaa27db0f03fb313ea46e1186e7d36cdcb1b6 | commitdiff |
kernel - Try to fix delayed mtime updates on SHARED+RW maps again
* Attempt to fix continuing problems with mtime updates related to
modifications made via SHARED+RW mmap()s. As evidenced by builds
under synth sometimes getting confused.
* Don't update vp->v_lastwrite_ts in vop_stdclose(). Instead, update
the field and set a new flag VLASTWRITETS upon mmap(SHARED+PROT_WRITE)
or upon mprotect(PROT_WRITE) on a SHARED mmap.
* Clear the flag on any regular write, utimes, or truncation.
* Adjust various filesystems to update mtime from vp->v_lastwrite_ts
only upon UIO_NOCOPY writes, and only if VLASTWRITETS is set.
tmpfs, ufs, hammer, hammer2 adjusted.
* Attempt to fix continuing problems with mtime updates related to
modifications made via SHARED+RW mmap()s. As evidenced by builds
under synth sometimes getting confused.
* Don't update vp->v_lastwrite_ts in vop_stdclose(). Instead, update
the field and set a new flag VLASTWRITETS upon mmap(SHARED+PROT_WRITE)
or upon mprotect(PROT_WRITE) on a SHARED mmap.
* Clear the flag on any regular write, utimes, or truncation.
* Adjust various filesystems to update mtime from vp->v_lastwrite_ts
only upon UIO_NOCOPY writes, and only if VLASTWRITETS is set.
tmpfs, ufs, hammer, hammer2 adjusted.
12 files changed: