BPF: Fix status_ not being set properly

- A typo prevented status_ from being set properly in
  supportsSeccompSandbox()
- Also fix a warning by explicitly discarding a return value

BUG=
TEST=
NOTRY=true


Review URL: https://chromiumcodereview.appspot.com/10532038

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140951 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 2 insertions, 2 deletions

diff --git a/sandbox/linux/seccomp-bpf/sandbox_bpf.cc b/sandbox/linux/seccomp-bpf/sandbox_bpf.cc
index a60b208..e7b1da6 100644
--- a/sandbox/linux/seccomp-bpf/sandbox_bpf.cc
+++ b/sandbox/linux/seccomp-bpf/sandbox_bpf.cc
@@ -94,7 +94,7 @@ Sandbox::SandboxStatus Sandbox::supportsSeccompSandbox(int proc_fd) {
     // In other words, if a single-threaded process is currently in the
     // STATUS_UNAVAILABLE state, it is safe to assume that sandboxing is
     // actually available.
-    status_ == STATUS_AVAILABLE;
+    status_ = STATUS_AVAILABLE;
     return status_;
   }
 
@@ -169,7 +169,7 @@ bool Sandbox::isSingleThreaded(int proc_fd) {
       sb.st_nlink != 3 ||
       HANDLE_EINTR(close(task))) {
     if (task >= 0) {
-      HANDLE_EINTR(close(task));
+      (void) HANDLE_EINTR(close(task));
     }
     return false;
   }