Syscall wrappers: Skip LStat test in ChromeOS

Within ChromeOS /tmp is mounted with nosymfollow. This causes
the LStat test to fail because symlinks cannot be followed.

The LStat test is updated to now skip when using ChromeOS.

BUG=b:240825790
TEST=Verify test is skipped when on ChromeOS

Change-Id: I03dd2117489af6935d16fc3a5790b1b31fa8ae84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3811141
Commit-Queue: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1032829}
NOKEYCHECK=True
GitOrigin-RevId: 2a011bc872a187a2501b4885f7815a35268817eb
1 file changed
tree: 5da033cc3309f3ca053b0f3985afb58413bb0ba7
  1. linux/
  2. mac/
  3. policy/
  4. win/
  5. BUILD.gn
  6. COMMON_METADATA
  7. constants.h
  8. DEPS
  9. DIR_METADATA
  10. features.cc
  11. features.gni
  12. features.h
  13. ipc.dict
  14. OWNERS
  15. README.md
  16. sandbox_export.h
README.md

Sandbox Library

This directory contains platform-specific sandboxing libraries. Sandboxing is a technique that can improve the security of an application by separating untrustworthy code (or code that handles untrustworthy data) and restricting its privileges and capabilities.

Each platform relies on the operating system's process primitive to isolate code into distinct security principals, and platform-specific technologies are used to implement the privilege reduction. At a high-level:

  • mac/ uses the Seatbelt sandbox. See the detailed design for more.
  • linux/ uses namespaces and Seccomp-BPF. See the detailed design for more.
  • win/ uses a combination of restricted tokens, distinct job objects, alternate desktops, and integrity levels. See the detailed design for more.

Built on top of the low-level sandboxing library is the //sandbox/policy component, which provides concrete policies and helper utilities for sandboxing specific Chromium processes and services. The core sandbox library cannot depend on the policy component.