summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2020-03-22 06:08:17 +0300
committerDavid S. Miller <davem@davemloft.net>2020-03-22 06:08:17 +0300
commite28596012d1a482641a2110ed1c4c09ce98562b3 (patch)
tree9c1964e017b681e310c7ec48352bd124da90930c /tools/perf/scripts/python/export-to-postgresql.py
parent26922c0ef33f2b24192f567db9d01ce4fa289b54 (diff)
parentd5bee7374b68de3c44586d46e9e61ffc97a1e886 (diff)
downloadlinux-e28596012d1a482641a2110ed1c4c09ce98562b3.tar.xz
Merge branch 'net-tls-Annotate-lockless-access-to-sk_prot'
Jakub Sitnicki says: ==================== net/tls: Annotate lockless access to sk_prot We have recently noticed that there is a case of lockless read/write to sk->sk_prot [0]. sockmap code on psock tear-down writes to sk->sk_prot, while holding sk_callback_lock. Concurrently, tcp can access it. Usually to read out the sk_prot pointer and invoke one of the ops, sk->sk_prot->handler(). The lockless write (lockless in regard to concurrent reads) happens on the following paths: tcp_bpf_{recvmsg|sendmsg} / sock_map_unref sk_psock_put sk_psock_drop sk_psock_restore_proto WRITE_ONCE(sk->sk_prot, proto) To prevent load/store tearing [1], and to make tooling aware of intentional shared access [2], we need to annotate sites that access sk_prot with READ_ONCE/WRITE_ONCE. This series kicks off the effort to do it. Starting with net/tls. [0] https://lore.kernel.org/bpf/a6bf279e-a998-84ab-4371-cd6c1ccbca5d@gmail.com/ [1] https://lwn.net/Articles/793253/ [2] https://github.com/google/ktsan/wiki/READ_ONCE-and-WRITE_ONCE ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions