From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH v3 mptcp-net 0/2] mptcp: fix another deadlock issue
Date: Thu, 22 Feb 2024 11:54:45 +0100 [thread overview]
Message-ID: <e98b8b07-558c-498a-97fb-dd5cab11e439@kernel.org> (raw)
In-Reply-To: <cover.1708539640.git.pabeni@redhat.com>
Hi Paolo,
On 21/02/2024 7:22 pm, Paolo Abeni wrote:
> 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.
Thank you for the patches!
Now in our tree (fixes for -net), with 2 small modifications to satisfy
CheckPatch [1]:
New patches for t/upstream-net and t/upstream:
- 5ca0931fda75: mptcp: fix possible deadlock in subflow diag
- 560736ee5851: selftests: mptcp: explicitly trigger the listener diag
code-path
- Results: b35846da7660..8f414384d341 (export-net)
- Results: df010bcea0cb..a542d2d60003 (export)
[1] https://github.com/multipath-tcp/mptcp_net-next/actions/runs/8002395030
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-02-22 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 18:22 [PATCH v3 mptcp-net 0/2] mptcp: fix another deadlock issue Paolo Abeni
2024-02-21 18:22 ` [PATCH v3 mptcp-net 1/2] mptcp: fix possible deadlock in subflow diag Paolo Abeni
2024-02-21 18:22 ` [PATCH v3 mptcp-net 2/2] selftests: mptcp: explicitly trigger the listener diag code-path Paolo Abeni
2024-02-21 19:14 ` selftests: mptcp: explicitly trigger the listener diag code-path: Tests Results MPTCP CI
2024-02-22 10:22 ` MPTCP CI
2024-02-22 9:26 ` [PATCH v3 mptcp-net 0/2] mptcp: fix another deadlock issue Matthieu Baerts
2024-02-22 10:54 ` Matthieu Baerts [this message]
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=e98b8b07-558c-498a-97fb-dd5cab11e439@kernel.org \
--to=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.com \
/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