summaryrefslogtreecommitdiffhomepage
path: root/pkg/sentry/fs/tty/fs.go
diff options
context:
space:
mode:
authorNicolas Lacasse <nlacasse@google.com>2018-07-19 14:56:42 -0700
committerShentubot <shentubot@google.com>2018-07-19 14:57:52 -0700
commitbe431d0934b8d33dcb1909527e0f9ed7eb504b6f (patch)
tree4071eb98e3ecdfa6abd77552c7e5426469027cd8 /pkg/sentry/fs/tty/fs.go
parentea371031968095209793ea39007cfdf5a9d66d10 (diff)
fs: Pass context to Revalidate() function.
The current revalidation logic is very simple and does not do much introspection of the dirent being revalidated (other than looking at the type of file). Fancier revalidation logic is coming soon, and we need to be able to look at the cached and uncached attributes of a given dirent, and we need a context to perform some of these operations. PiperOrigin-RevId: 205307351 Change-Id: If17ea1c631d8f9489c0e05a263e23d7a8a3bf159
Diffstat (limited to 'pkg/sentry/fs/tty/fs.go')
-rw-r--r--pkg/sentry/fs/tty/fs.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/pkg/sentry/fs/tty/fs.go b/pkg/sentry/fs/tty/fs.go
index 1ef1a85e3..dbaffe95e 100644
--- a/pkg/sentry/fs/tty/fs.go
+++ b/pkg/sentry/fs/tty/fs.go
@@ -78,7 +78,7 @@ type superOperations struct{}
// Slave entries are dropped from dir when their master is closed, so an
// existing slave Dirent in the tree is not sufficient to guarantee that it
// still exists on the filesystem.
-func (superOperations) Revalidate(*fs.Dirent) bool {
+func (superOperations) Revalidate(context.Context, *fs.Dirent) bool {
return true
}