From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Cc: Christoph Paasch <cpaasch@apple.com>
Subject: [PATCH mptcp-net 0/4] mptcp: a bunch of data race fixes
Date: Wed, 17 May 2023 13:35:32 +0200 [thread overview]
Message-ID: <cover.1684321532.git.pabeni@redhat.com> (raw)
The first 2 patches are direct response to recently reported KCSAN
splat.
The later 2 are just by code inspection of related code path. Patch 3/4
is there mostly to make the next one simple, even if the race mentioned
in such patch should be real (but very tiny, if possible at all).
Paolo Abeni (4):
mptcp: add annotations around msk->subflow accesses
mptcp: consolidate passive msk socket initialization
mptcp: fix data race around msk->first access
mptcp: add annotations around sk->sk_shutdown accesses
net/mptcp/protocol.c | 86 ++++++++++++++++++++++++++++----------------
net/mptcp/protocol.h | 14 +++++---
net/mptcp/subflow.c | 28 +--------------
3 files changed, 66 insertions(+), 62 deletions(-)
--
2.40.1
next reply other threads:[~2023-05-17 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 11:35 Paolo Abeni [this message]
2023-05-17 11:35 ` [PATCH mptcp-net 1/4] mptcp: add annotations around msk->subflow accesses Paolo Abeni
2023-05-17 11:35 ` [PATCH mptcp-net 2/4] mptcp: consolidate passive msk socket initialization Paolo Abeni
2023-05-17 14:12 ` kernel test robot
2023-05-17 18:26 ` kernel test robot
2023-05-17 11:35 ` [PATCH mptcp-net 3/4] mptcp: fix data race around msk->first access Paolo Abeni
2023-05-17 11:35 ` [PATCH mptcp-net 4/4] mptcp: add annotations around sk->sk_shutdown accesses Paolo Abeni
2023-05-17 12:05 ` mptcp: add annotations around sk->sk_shutdown accesses: Build Failure MPTCP CI
2023-05-17 13:10 ` mptcp: add annotations around sk->sk_shutdown accesses: Tests Results MPTCP CI
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1684321532.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=cpaasch@apple.com \
--cc=mptcp@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.