Page MenuHomeFreeBSD

tcp: improve validation of received TCP over UDP packets
ClosedPublic

Authored by tuexen on Fri, Feb 20, 8:46 PM.
Tags
None
Referenced Files
F145654419: D55410.diff
Sun, Feb 22, 5:20 PM
Unknown Object (File)
Fri, Feb 20, 9:17 PM

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

pouria added a subscriber: pouria.

LGTM

sys/netinet/tcp_subr.c
623

__predict_false?

I'd suggest to change to title to explictily say "TCP over UDP", cause "TCP/UDP" can be misinterpreted to a change to TCP and a similar change to UDP.

tuexen retitled this revision from tcp: improve validation of received TCP/UDP packets to tcp: improve validation of received TCP over UDP packets.Fri, Feb 20, 9:12 PM
This revision is now accepted and ready to land.Fri, Feb 20, 9:17 PM
tuexen added inline comments.
sys/netinet/tcp_subr.c
623

Will put that in a cleanup I will make.

I agree on @pouria's comment.

A __predict_false makes sense in the IPv6 case as well.

I agree on @pouria's comment.

A __predict_false makes sense in the IPv6 case as well.

Had to do the same for SBR-ILNP for IPv6 vs ILNPv6 flows, in ip6_forward(), when deciding whether or not to call ilnp6_forward(), which currently exists only in the sup3r s3krt bms dSBR-ILNP branch. @rgrimes will probably not have to deal with this as it wasn't really a issue for hosts.

Currently busy spinning up on SRv6. The code archeaology of FreeBSD vs source routing is a story for another time. I see @gnn knows where some of the bodies are buried there.

I agree on @pouria's comment.

A __predict_false makes sense in the IPv6 case as well.

Done in D55415.