diff options
| author | Guillaume Nault <gnault@redhat.com> | 2019-12-06 12:38:49 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-12-21 10:57:19 +0100 |
| commit | fbcf85b047aaf17d7cb91e46f42c12b106a9138d (patch) | |
| tree | 1bb92522abd74fafe26c5b85a44fc6e55927187a /firmware | |
| parent | 4b8a98697a79f939f4275e4b09a47315e70bd537 (diff) | |
| download | linux-stable-fbcf85b047aaf17d7cb91e46f42c12b106a9138d.tar.gz linux-stable-fbcf85b047aaf17d7cb91e46f42c12b106a9138d.tar.bz2 linux-stable-fbcf85b047aaf17d7cb91e46f42c12b106a9138d.zip | |
tcp: Protect accesses to .ts_recent_stamp with {READ,WRITE}_ONCE()
[ Upstream commit 721c8dafad26ccfa90ff659ee19755e3377b829d ]
Syncookies borrow the ->rx_opt.ts_recent_stamp field to store the
timestamp of the last synflood. Protect them with READ_ONCE() and
WRITE_ONCE() since reads and writes aren't serialised.
Use of .rx_opt.ts_recent_stamp for storing the synflood timestamp was
introduced by a0f82f64e269 ("syncookies: remove last_synq_overflow from
struct tcp_sock"). But unprotected accesses were already there when
timestamp was stored in .last_synq_overflow.
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Guillaume Nault <gnault@redhat.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions