summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2024-02-05 11:18:10 +0000
committerDavid S. Miller <davem@davemloft.net>2024-02-05 11:18:10 +0000
commitc3b39ea2371b283d4faf5e69be6c41d1bf3f7957 (patch)
treee53ee1def28cd6c5dc681c6f51ee01dbaf422725 /lib
parent1e08223272c7bd5b26196389fab3892ba9942be3 (diff)
parent28e5c138050670e813017102c1ac842a6a0aa297 (diff)
downloadlinux-stable-c3b39ea2371b283d4faf5e69be6c41d1bf3f7957.tar.gz
linux-stable-c3b39ea2371b283d4faf5e69be6c41d1bf3f7957.tar.bz2
linux-stable-c3b39ea2371b283d4faf5e69be6c41d1bf3f7957.zip
Merge branch 'mptcp-annotate-lockless'
Matthieu Baerts says: ==================== mptcp: annotate lockless access This is a series of 5 patches from Paolo to annotate lockless access. The MPTCP locking schema is already quite complex. We need to clarify it and make the lockless access already there consistent, or later changes will be even harder to follow and understand. This series goes through all the msk fields accessed in the RX and TX path and makes the lockless annotation consistent with the in-use locking schema. As a bonus, this should fix data races eventually found by fuzzers -- even if we haven't seen many such reports so far. Patch 1/5 hints we could remove "local_key" and "remote_key" from the subflow context, and always use the ones from the msk socket, possibly reducing the context memory usage. That change is left over as a possible follow-up. ==================== Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions