summaryrefslogtreecommitdiffhomepage
path: root/pkg/sentry/fs/host
diff options
context:
space:
mode:
authorMichael Pratt <mpratt@google.com>2020-06-17 12:32:59 -0700
committergVisor bot <gvisor-bot@google.com>2020-06-17 12:34:33 -0700
commit6d806ee7198422973a2e4efa9b539de7792b933f (patch)
tree460a7f620751543e0470977979068b70a1618910 /pkg/sentry/fs/host
parente5d97cbcc1e64185b8fab1cf563c8754edd2e52e (diff)
Remove various uses of 'blacklist'
Updates #2972 PiperOrigin-RevId: 316942245
Diffstat (limited to 'pkg/sentry/fs/host')
-rw-r--r--pkg/sentry/fs/host/tty.go6
1 files changed, 3 insertions, 3 deletions
diff --git a/pkg/sentry/fs/host/tty.go b/pkg/sentry/fs/host/tty.go
index cb91355ab..82a02fcb2 100644
--- a/pkg/sentry/fs/host/tty.go
+++ b/pkg/sentry/fs/host/tty.go
@@ -308,9 +308,9 @@ func (t *TTYFileOperations) checkChange(ctx context.Context, sig linux.Signal) e
task := kernel.TaskFromContext(ctx)
if task == nil {
// No task? Linux does not have an analog for this case, but
- // tty_check_change is more of a blacklist of cases than a
- // whitelist, and is surprisingly permissive. Allowing the
- // change seems most appropriate.
+ // tty_check_change only blocks specific cases and is
+ // surprisingly permissive. Allowing the change seems
+ // appropriate.
return nil
}