[roll] Roll fuchsia [Starnix] Resolve socket protocol on socket creation

Socket stores `protocol` field. Previously it was always set to the
value passed to `socket()` syscall during creation. The syscall allows
`protocol` parameter to be set to 0, which case the actual protocol
used by the socket is either TCP or UDP depending on the socket type
parameter. Updated `Socket::new()` to resolve the packet type, which
ensures the correct value is stored in the struct. This will allow
to pass correct protocol value to eBPF programs executed in Starnix.

Original-Bug: 391380601
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1201768
Original-Revision: 1f2292fe5d973217f3d3d678eda6d5d330998981
GitOrigin-RevId: bd17ed145b2abee817d514f016df1c3f5261d4b5
Change-Id: I1404099fd59ba11fb1177fee22a338da700db354
1 file changed
tree: f2da386ec29e417e7a21f658e6e900c744a4b4da
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.