Skip to content

fix(tcpip): keep readv dispatcher alive after filtered frame - #14448

Open
tianyuzhou95 wants to merge 1 commit into
google:masterfrom
tianyuzhou95:albert/fdbased-foreign-frame
Open

fix(tcpip): keep readv dispatcher alive after filtered frame#14448
tianyuzhou95 wants to merge 1 commit into
google:masterfrom
tianyuzhou95:albert/fdbased-foreign-frame

Conversation

@tianyuzhou95

Copy link
Copy Markdown
Contributor

Treat an Ethernet frame rejected by the endpoint address filter as a consumed packet rather than a request to stop the ReadV dispatch loop.

A direct TAP endpoint can receive foreign unicast traffic after a sandbox is restored and reattached to a bridge with stale FDB or neighbor state. Returning false for that frame tears down the receive dispatcher, leaving the restored sandbox running but unable to receive subsequent traffic.

Keep the dispatcher alive after dropping the frame, matching the RecvMMsg and PacketMMap paths.

Treat an Ethernet frame rejected by the endpoint address filter as a
consumed packet rather than a request to stop the ReadV dispatch loop.

A direct TAP endpoint can receive foreign unicast traffic after a sandbox
is restored and reattached to a bridge with stale FDB or neighbor state.
Returning false for that frame tears down the receive dispatcher, leaving
the restored sandbox running but unable to receive subsequent traffic.

Keep the dispatcher alive after dropping the frame, matching the RecvMMsg
and PacketMMap paths.

Signed-off-by: Tianyu Zhou <albert.zty@antgroup.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant