fix reuseaddr regression
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | net: set tb->fast_sk_familynet/ | +2 | 0 replies | |
| 2/3 | net: use inet6_rcv_saddr to compare socketsnet/ | +1 | 0 replies | |
| 3/3 | inet: fix improper empty comparisonnet/ | +1 | 0 replies |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by.
| Patch | Cole Robinson |
|---|---|
| 1/3 | Reported-and-tested-by |
| 2/3 | Reported-and-tested-by |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] fix reuseaddr regression
I introduced a regression when reworking the fastreuse port stuff that allows bind conflicts to occur once a reuseaddr socket successfully opens on an existing tb. The root cause is I reversed an if statement which caused us to set the tb as if there were no owners on the socket if there were, which obviously is not correct.
Dave I have follow up patches that will add a selftest for this case and I ran the other reuseport related tests as well. These need to go in pretty quickly as it breaks kvm, I've marked them for stable. Sorry for the regression,
Josef