[roll] Roll fuchsia [Netstack3] Cleanup handling of unrecognized Next Header
Updated IPv6 extension parsing to handle the following 3 cases
correctly:
1. Ipv6PacketRaw parser now stops extension header parsing at
unrecognized Next Header field instead of trying to parse it.
Previously it tried to parse it as an extension, but that
is an incorrect assumption (e.g. for SCTP packets).
2. Proper error is returned now when encountering unrecognized
Next Header in an extension header.
3. Now Next Header field in extension headers is validated only
after parsing the header itself (as required by the RFC).
Original-Original-Bug: 517305535, 525414145
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1681994
Original-Original-Revision: bef362d4c5d3fe42128d4489a689d8047e06399e
GitOrigin-RevId: 4d792bfc3ebe349490247e791c745036684c4c08
Change-Id: I5bf5ab3192f88af41ff9f7f8939fefaffc661de8
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1682589
Cr-Commit-Position: refs/heads/main@{#195706}
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.