From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v2 mptcp-net 0/2] mptcp: fix another deadlock issue
Date: Wed, 21 Feb 2024 16:32:15 +0100 [thread overview]
Message-ID: <cover.1708529444.git.pabeni@redhat.com> (raw)
Eric reported and diagnosed another possible deadlock problem with
the MPTCP diag code. The first patch address the issue, and the second
adds self-test coverage for the relevant codepath, to get lockdep help
to catch future similar issues.
following-up with the netdev fiasco, sending on mptcp only
v1 -> v2:
- fix (avoid) feature detection in patch 2/2 (Matttbe)
Paolo Abeni (2):
mptcp: fix possible deadlock in subflow diag
selftests: mptcp: explicitly trigger the listener diag code-path
net/mptcp/diag.c | 3 +++
tools/testing/selftests/net/mptcp/diag.sh | 24 +++++++++++++++++++++++
2 files changed, 27 insertions(+)
--
2.43.0
next reply other threads:[~2024-02-21 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 15:32 Paolo Abeni [this message]
2024-02-21 15:32 ` [PATCH v2 mptcp-net 1/2] mptcp: fix possible deadlock in subflow diag Paolo Abeni
2024-02-21 15:32 ` [PATCH v2 mptcp-net 2/2] selftests: mptcp: explicitly trigger the listener diag code-path Paolo Abeni
2024-02-21 16:22 ` selftests: mptcp: explicitly trigger the listener diag code-path: Tests Results MPTCP CI
2024-02-21 15:40 ` [PATCH v2 mptcp-net 0/2] mptcp: fix another deadlock issue Matthieu Baerts
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.1708529444.git.pabeni@redhat.com \
--to=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox