From: Shardul Bankar <shardulsb08@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>,
matttbe@kernel.org, martineau@kernel.org
Cc: geliang@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, horms@kernel.org, netdev@vger.kernel.org,
mptcp@lists.linux.dev, linux-kernel@vger.kernel.org,
janak@mpiric.us, kalpan.jani@mpiricsoftware.com
Subject: Re: [PATCH] mptcp: do not drop partial packets
Date: Wed, 22 Apr 2026 20:10:42 +0530 [thread overview]
Message-ID: <dfbb7837823c2ffe0f6b1bdbfbaae71164cd7ba6.camel@gmail.com> (raw)
In-Reply-To: <fc2ca10a-1fa8-48f8-b140-6c59595fc08b@redhat.com>
On Wed, 2026-04-22 at 15:51 +0200, Paolo Abeni wrote:
> On 4/22/26 2:09 PM, Shardul Bankar wrote:
> > +
> > + /* Partial packet: map_seq < ack_seq < end_seq.
> > + * Skip the already-acked bytes and enqueue the new data.
> > */
> > - MPTCP_INC_STATS(sock_net(sk), MPTCP_MIB_DUPDATA);
> > - mptcp_drop(sk, skb);
> > - return false;
> > + copy_len = MPTCP_SKB_CB(skb)->end_seq - msk->ack_seq;
> > + MPTCP_SKB_CB(skb)->offset += msk->ack_seq -
> > MPTCP_SKB_CB(skb)->map_seq;
>
> here MPTCP_SKB_CB(skb)->offset is always != 0 ...
>
> > + msk->bytes_received += copy_len;
> > + WRITE_ONCE(msk->ack_seq, msk->ack_seq + copy_len);
> > + tail = skb_peek_tail(&sk->sk_receive_queue);
> > + if (tail && mptcp_try_coalesce(sk, tail, skb))
>
> ... so mptcp_try_coalesce() will always fail.
Thanks, good catch. Fixed in v2.
Regards,
Shardul
prev parent reply other threads:[~2026-04-22 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 12:09 [PATCH] mptcp: do not drop partial packets Shardul Bankar
2026-04-22 13:51 ` Paolo Abeni
2026-04-22 14:40 ` Shardul Bankar [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=dfbb7837823c2ffe0f6b1bdbfbaae71164cd7ba6.camel@gmail.com \
--to=shardulsb08@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=janak@mpiric.us \
--cc=kalpan.jani@mpiricsoftware.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--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