gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2021-08-27	Add LinkEndpoint.WriteRawPacket with stubs	Ghanan Gowripalan
	...returning unsupported errors. PiperOrigin-RevId: 393388991
2021-04-21	Only carry GSO options in the packet buffer	Ghanan Gowripalan
	With this change, GSO options no longer needs to be passed around as a function argument in the write path. This change is done in preparation for a later change that defers segmentation, and may change GSO options for a packet as it flows down the stack. Updates #170. PiperOrigin-RevId: 369774872
2021-02-06	Synchronously send packets over pipe link endpoint	Ghanan Gowripalan
	Before this change, packets were delivered asynchronously to the remote end of a pipe. This was to avoid a deadlock during link resolution where the stack would attempt to double-lock a mutex (see removed comments in the parent commit for details). As of https://github.com/google/gvisor/commit/4943347137, we do not hold locks while sending link resolution probes so the deadlock will no longer occur. PiperOrigin-RevId: 356066224
2021-01-28	Change tcpip.Error to an interface	Tamir Duberstein
	This makes it possible to add data to types that implement tcpip.Error. ErrBadLinkEndpoint is removed as it is unused. PiperOrigin-RevId: 354437314
2021-01-21	Queue packets in WritePackets when resolving link address	Ghanan Gowripalan
	Test: integration_test.TestWritePacketsLinkResolution Fixes #4458. PiperOrigin-RevId: 353108826
2021-01-15	Support GetLinkAddress with neighborCache	Ghanan Gowripalan
	Test: integration_test.TestGetLinkAddress PiperOrigin-RevId: 352119404
2021-01-15	Only pass stack.Route's fields to LinkEndpoints	Ghanan Gowripalan
	stack.Route is used to send network packets and resolve link addresses. A LinkEndpoint does not need to do either of these and only needs the route's fields at the time of the packet write request. Since LinkEndpoints only need the route's fields when writing packets, pass a stack.RouteInfo instead. PiperOrigin-RevId: 352108405
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