diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-04-18 21:10:15 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-04-18 21:10:16 +0300 |
| commit | f3a0e90d4deb6386b90a9d5233028259c441cbc1 (patch) | |
| tree | c01a7b3b1b7bee880edd6529ab29cab2c75cdd69 /include/linux | |
| parent | 82c21069028c5db3463f851ae8ac9cc2e38a3827 (diff) | |
| parent | 9e89b9d03a2d2e30dcca166d5af52f9a8eceab25 (diff) | |
| download | linux-f3a0e90d4deb6386b90a9d5233028259c441cbc1.tar.xz | |
Merge branch 'tcp-take-care-of-tcp_get_timestamping_opt_stats-races'
Eric Dumazet says:
====================
tcp: take care of tcp_get_timestamping_opt_stats() races
tcp_get_timestamping_opt_stats() does not own the socket lock,
this is intentional.
It calls tcp_get_info_chrono_stats() while other threads could
change chrono fields in tcp_chrono_set(). It also reads many
tcp socket fields that can be modified by other cpus/threads.
I do not think we need coherent TCP socket state snapshot
in tcp_get_timestamping_opt_stats().
Add READ_ONCE()/WRITE_ONCE() or data_race() annotations.
Note that icsk_ca_state is a bitfield, thus not covered
in this series.
====================
Link: https://patch.msgid.link/20260416200319.3608680-1-edumazet@google.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions
