From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net v3 3/6] Squash-to: "mptcp: invoke MP_FAIL response when needed"
Date: Fri, 17 Jun 2022 16:06:14 -0700 (PDT) [thread overview]
Message-ID: <b6d4766-c366-224c-548-afa65115d94c@linux.intel.com> (raw)
In-Reply-To: <3c73bf6e5c29fd1639a2ce0ccc93b06f5a49a335.camel@redhat.com>
On Fri, 17 Jun 2022, Paolo Abeni wrote:
> On Fri, 2022-06-17 at 12:05 +0200, Paolo Abeni wrote:
>> diff --git a/net/mptcp/subflow.c b/net/mptcp/subflow.c
>> index 98b12a9c4eb5..c82a9a6e0267 100644
>> --- a/net/mptcp/subflow.c
>> +++ b/net/mptcp/subflow.c
>> @@ -1158,6 +1158,33 @@ static bool subflow_can_fallback(struct mptcp_subflow_context *subflow)
>> return !subflow->fully_established;
>> }
>>
>> +static void mptcp_subflow_fail(struct mptcp_sock *msk, struct sock *ssk)
>> +{
>> + struct mptcp_subflow_context *subflow = mptcp_subflow_ctx(ssk);
>> + unsigned long fail_tout;
>> +
>> + /* grecefull failure can happen only on the MPC subflow */
>> + if (WARN_ON_ONCE(ssk != READ_ONCE(msk->first)))
>> + return;
>> +
>> + /* since the close timeout take precedence on the fail one,
>> + * no need to starte the latter when the first is already set
>
> Typo here ("starte"). It would be great if it could be addressed
> without reposting the whole series... A later squash-to patch could be
> ok?
>
Typo fix via squash or edit is fine by me. Also, grecefull->graceful a
few lines earlier.
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-06-17 23:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:05 [PATCH mptcp-net v3 0/6] mptcp: mp_fail related fixes Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 1/6] mptcp: fix error mibs accounting Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 2/6] mptcp: introduce MAPPING_BAD_CSUM Paolo Abeni
2022-06-17 23:13 ` Mat Martineau
2022-06-20 9:24 ` Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 3/6] Squash-to: "mptcp: invoke MP_FAIL response when needed" Paolo Abeni
2022-06-17 14:01 ` Paolo Abeni
2022-06-17 23:06 ` Mat Martineau [this message]
2022-06-17 10:05 ` [PATCH mptcp-net v3 4/6] mptcp: fix shutdown vs fallback race Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 5/6] mptcp: consistent map handling on failure Paolo Abeni
2022-06-17 10:05 ` [PATCH mptcp-net v3 6/6] mptcp: fix race on unaccepted mptcp sockets Paolo Abeni
2022-06-17 11:57 ` mptcp: fix race on unaccepted mptcp sockets: Tests Results MPTCP CI
2022-06-18 0:51 ` [PATCH mptcp-net v3 6/6] mptcp: fix race on unaccepted mptcp sockets Mat Martineau
2022-06-20 10:15 ` Paolo Abeni
2022-06-20 10:47 ` Paolo Abeni
2022-06-17 23:05 ` [PATCH mptcp-net v3 0/6] mptcp: mp_fail related fixes Mat Martineau
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=b6d4766-c366-224c-548-afa65115d94c@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--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