gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-12-03	Make `stack.Route` thread safe	Peter Johnston
	Currently we rely on the user to take the lock on the endpoint that owns the route, in order to modify it safely. We can instead move `Route.RemoteLinkAddress` under `Route`'s mutex, and allow non-locking and thread-safe access to other fields of `Route`. PiperOrigin-RevId: 345461586
2020-11-18	Introduce stack.WritePacketToRemote, remove LinkEndpoint.WriteRawPacket	Bruno Dal Bo
	Redefine stack.WritePacket into stack.WritePacketToRemote which lets the NIC decide whether to append link headers. PiperOrigin-RevId: 343071742
2020-10-16	Don't include link header when forwarding packets	Ghanan Gowripalan
	Before this change, if a link header was included in an incoming packet that is forwarded, the packet that gets sent out will take the original packet and add a link header to it while keeping the old link header. This would make the sent packet look like: OUTGOING LINK HDR \| INCOMING LINK HDR \| NETWORK HDR \| ... Obviously this is incorrect as we should drop the incoming link header and only include the outgoing link header. This change fixes this bug. Test: integration_test.TestForwarding PiperOrigin-RevId: 337571447
2020-10-09	Automated rollback of changelist 336304024	Ghanan Gowripalan
	PiperOrigin-RevId: 336339194
2020-10-09	Automated rollback of changelist 336185457	Bhasker Hariharan
	PiperOrigin-RevId: 336304024
2020-10-08	Do not resolve routes immediately	Ghanan Gowripalan
	When a response needs to be sent to an incoming packet, the stack should consult its neighbour table to determine the remote address's link address. When an entry does not exist in the stack's neighbor table, the stack should queue the packet while link resolution completes. See comments. PiperOrigin-RevId: 336185457