diff options
| author | Eric Dumazet <[email protected]> | 2022-04-05 16:35:38 -0700 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2022-04-06 12:05:41 -0700 |
| commit | 40570375356c874b1578e05c1dcc3ff7c1322dbe (patch) | |
| tree | 54c7a52bfdd4e302f877e93dc94adb09cfa3aac4 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 487dc3ca60e3e420d54bcc613cb49e8e85f34569 (diff) | |
tcp: add accessors to read/set tp->snd_cwnd
We had various bugs over the years with code
breaking the assumption that tp->snd_cwnd is greater
than zero.
Lately, syzbot reported the WARN_ON_ONCE(!tp->prior_cwnd) added
in commit 8b8a321ff72c ("tcp: fix zero cwnd in tcp_cwnd_reduction")
can trigger, and without a repro we would have to spend
considerable time finding the bug.
Instead of complaining too late, we want to catch where
and when tp->snd_cwnd is set to an illegal value.
Signed-off-by: Eric Dumazet <[email protected]>
Suggested-by: Yuchung Cheng <[email protected]>
Cc: Neal Cardwell <[email protected]>
Acked-by: Yuchung Cheng <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions