Fabricio Voznika dd3bc49997 Add NAME_MAX checks and update file times ... NAME_MAX should be enforced per filesystem implementation because other file systems may not have the same restriction. Gofer filesystem now keeps a reference to the kernel clock to avoid lookup in the Context on file access to update atime. Update access, modification, and status change times in tmpfs. Updates #1197, #1198. PiperOrigin-RevId: 304527148		2020-04-02 19:39:03 -07:00
..
BUILD	Add BoundEndpointAt filesystem operation.	2020-03-26 21:52:24 -07:00
directory.go	Add NAME_MAX checks and update file times	2020-04-02 19:39:03 -07:00
filesystem.go	Add NAME_MAX checks and update file times	2020-04-02 19:39:03 -07:00
gofer.go	Add NAME_MAX checks and update file times	2020-04-02 19:39:03 -07:00
handle.go	VFS2 gofer client	2020-02-04 11:29:22 -08:00
handle_unsafe.go	VFS2 gofer client	2020-02-04 11:29:22 -08:00
p9file.go	VFS2 gofer client	2020-02-04 11:29:22 -08:00
pagemath.go	VFS2 gofer client	2020-02-04 11:29:22 -08:00
regular_file.go	Add NAME_MAX checks and update file times	2020-04-02 19:39:03 -07:00
special_file.go	Add NAME_MAX checks and update file times	2020-04-02 19:39:03 -07:00
symlink.go	Add NAME_MAX checks and update file times	2020-04-02 19:39:03 -07:00
time.go	Add NAME_MAX checks and update file times	2020-04-02 19:39:03 -07:00