Page MenuHomeFreeBSD

tcp: update error counter when dropping a packet due to bad source
ClosedPublic

Authored by glebius on Mar 23 2023, 9:54 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jan 14 2024, 7:35 AM
Unknown Object (File)
Dec 20 2023, 8:17 AM
Unknown Object (File)
Nov 12 2023, 1:10 PM
Unknown Object (File)
Oct 9 2023, 12:09 PM
Unknown Object (File)
Jun 30 2023, 3:21 AM
Unknown Object (File)
Jun 24 2023, 8:30 AM
Unknown Object (File)
Jun 24 2023, 5:10 AM
Unknown Object (File)
May 19 2023, 7:13 PM

Details

Summary

Use the same counter that ip_input()/ip6_input() use for bad destination
address. For IPv6 this is already heavily abused ip6s_badscope, which
needs to be split into several separate error counters.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

tuexen added inline comments.
sys/netinet/tcp_input.c
678

Why do you keep the /* XXX */ in one case, but not in the other. I suggest to be consistent.

markj added inline comments.
sys/netinet/tcp_input.c
678

For v4, badaddr seems like a reasonable counter. Here, the use of badscope is overloaded, I believe the XXX comment indicates that this is not the right counter. However, it's better than not counting at all.

sys/netinet/tcp_input.c
678

Yes, exactly what Mark said. :)

This revision was not accepted when it landed; it landed in state Needs Review.Mar 28 2023, 1:38 AM
This revision was automatically updated to reflect the committed changes.