mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
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 2/6] mptcp: introduce MAPPING_BAD_CSUM
Date: Fri, 17 Jun 2022 16:13:07 -0700 (PDT)	[thread overview]
Message-ID: <4a8c5ba-f234-9623-a36-ba3235744bf@linux.intel.com> (raw)
In-Reply-To: <dd078642fb80c4bb1f3184393cee1907026df46c.1655460262.git.pabeni@redhat.com>

On Fri, 17 Jun 2022, Paolo Abeni wrote:

> This allow moving a couple of conditional out of the fast path,
> making the code more easy to follow and will simplify the next
> patch.
>
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>

I've had a few rounds of feedback from Jakub about the Fixes: tag in the 
last few months - whether missing for -net or questionable inclusion in 
net-next... So I'd like to get this right :)

Given that this is tied to the following patch ("mptcp: invoke MP_FAIL 
response when needed"), and that patch "Fixes:" a patch that's only in the 
5.19rc series, I don't think a missing tag here is harmful. But I'm not 
sure what Jakub will want.

One option is to duplicate the "Fixes: d9fb797046c5" line from "mptcp: 
invoke MP_FAIL response when needed".

What do you think Paolo?


- Mat

> ---
> net/mptcp/subflow.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/net/mptcp/subflow.c b/net/mptcp/subflow.c
> index 57d2d8d933d0..98b12a9c4eb5 100644
> --- a/net/mptcp/subflow.c
> +++ b/net/mptcp/subflow.c
> @@ -843,7 +843,8 @@ enum mapping_status {
> 	MAPPING_INVALID,
> 	MAPPING_EMPTY,
> 	MAPPING_DATA_FIN,
> -	MAPPING_DUMMY
> +	MAPPING_DUMMY,
> +	MAPPING_BAD_CSUM
> };
>
> static void dbg_bad_map(struct mptcp_subflow_context *subflow, u32 ssn)
> @@ -958,9 +959,7 @@ static enum mapping_status validate_data_csum(struct sock *ssk, struct sk_buff *
> 				 subflow->map_data_csum);
> 	if (unlikely(csum)) {
> 		MPTCP_INC_STATS(sock_net(ssk), MPTCP_MIB_DATACSUMERR);
> -		if (subflow->mp_join || subflow->valid_csum_seen)
> -			subflow->send_mp_fail = 1;
> -		return subflow->mp_join ? MAPPING_INVALID : MAPPING_DUMMY;
> +		return MAPPING_BAD_CSUM;
> 	}
>
> 	subflow->valid_csum_seen = 1;
> @@ -1178,10 +1177,8 @@ static bool subflow_check_data_avail(struct sock *ssk)
>
> 		status = get_mapping_status(ssk, msk);
> 		trace_subflow_check_data_avail(status, skb_peek(&ssk->sk_receive_queue));
> -		if (unlikely(status == MAPPING_INVALID))
> -			goto fallback;
> -
> -		if (unlikely(status == MAPPING_DUMMY))
> +		if (unlikely(status == MAPPING_INVALID || status == MAPPING_DUMMY ||
> +			     status == MAPPING_BAD_CSUM))
> 			goto fallback;
>
> 		if (status != MAPPING_OK)
> @@ -1223,7 +1220,10 @@ static bool subflow_check_data_avail(struct sock *ssk)
> fallback:
> 	if (!__mptcp_check_fallback(msk)) {
> 		/* RFC 8684 section 3.7. */
> -		if (subflow->send_mp_fail) {
> +		if (status == MAPPING_BAD_CSUM &&
> +		    ((subflow->mp_join || subflow->valid_csum_seen))) {
> +			subflow->send_mp_fail = 1;
> +
> 			if (!READ_ONCE(msk->allow_infinite_fallback)) {
> 				ssk->sk_err = EBADMSG;
> 				tcp_set_state(ssk, TCP_CLOSE);
> -- 
> 2.35.3
>
>
>

--
Mat Martineau
Intel

  reply	other threads:[~2022-06-17 23:13 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 [this message]
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
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=4a8c5ba-f234-9623-a36-ba3235744bf@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;
as well as URLs for NNTP newsgroup(s).