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)
Dec 27 2024, 10:34 PM
Unknown Object (File)
Nov 15 2024, 6:10 AM
Unknown Object (File)
Oct 30 2024, 7:35 PM
Unknown Object (File)
Oct 22 2024, 7:51 AM
Unknown Object (File)
Oct 19 2024, 8:08 PM
Unknown Object (File)
Oct 16 2024, 12:38 PM
Unknown Object (File)
Sep 23 2024, 4:56 AM
Unknown Object (File)
Sep 20 2024, 12:52 AM

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.