[starnix] Split overloaded FsNode::socket field

This field had two jobs: For FDs created by syscalls like `socket()`, it
held the underlying socket so socket syscalls could access it through
the FD. For unix domain socket nodes, it held the socket bound to that
node. It turns out that for the first type of FD the socket is already
held by the FileOps, and nothing needs to access it through the FsNode.
So switch the first type of field accessors to go through the FileOps,
and rename the field to `bound_socket` for use for bound unix domain
sockets.

Change-Id: Ib917b76e33d5ec2f5266ca7fce585329786f407c
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1121712
Reviewed-by: Adam Barth <abarth@google.com>
Commit-Queue: Benjamin Lerman <qsr@google.com>
7 files changed
tree: 1930e0015d3e737f2bbe4509bf356ef304498f6b
  1. boards/
  2. build/
  3. bundles/
  4. docs/
  5. examples/
  6. infra/
  7. products/
  8. scripts/
  9. sdk/
  10. src/
  11. third_party/
  12. tools/
  13. zircon/
  14. .clang-format
  15. .clang-tidy
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gitmodules
  21. .gn
  22. .ignore
  23. analysis_options.yaml
  24. AUTHORS
  25. BUILD.gn
  26. CODE_OF_CONDUCT.md
  27. CONTRIBUTING.md
  28. fuchsia.code-workspace
  29. LICENSE
  30. OWNERS
  31. PATENTS
  32. pyproject.toml
  33. pyrightconfig.json
  34. README.md
  35. rustfmt.toml
  36. shac.star
  37. shac.textproto
README.md

Fuchsia

What is Fuchsia?

Fuchsia is an open source, general purpose operating system supporting modern 64-bit Intel and ARM processors.

We expect everyone interacting with our project to respect our code of conduct.

Read more about Fuchsia's principles.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.