All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Kalpan Jani <kalpan.jani@mpiricsoftware.com>,
	mptcp <mptcp@lists.linux.dev>
Cc: martineau <martineau@kernel.org>,
	"shardul.b" <shardul.b@mpiricsoftware.com>,
	janak <janak@mpiric.us>, kalpanjani009 <kalpanjani009@gmail.com>,
	shardulsb08 <shardulsb08@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>,
	syzkaller <syzkaller@googlegroups.com>,
	Akshit Patadiya <akshit@mpiricsoftware.com>
Subject: Re: [PATCH net v4] mptcp: fix stale skb->sk reference on subflow close
Date: Thu, 25 Jun 2026 10:06:47 +0200	[thread overview]
Message-ID: <ee4535dc-81e9-43a8-9b4c-e43be89e1628@kernel.org> (raw)
In-Reply-To: <19efd82a727.5577df63663915.5557063534077196375@mpiricsoftware.com>

Hi Kalpan,

On 25/06/2026 08:40, Kalpan Jani wrote:
> Hi Paolo, Matt,
> 
> Gentle ping on this patch.
> 
> https://lore.kernel.org/all/20260601083010.924938-1-kalpan.jani@mpiricsoftware.com/
> 
> I haven't seen any further feedback on v4, so I just wanted to bring it back to your attention in case it was missed.

Sorry for the delay, your patch has not been missed, it is tracked on
patchwork. The delay is due to unfortunate timing from most of us at the
same time, hopefully this will get better at the point, and the load
will decrease!

I will apply the patch, the v4 looks good to me.

> Changes since v3:
> - Rewrote the commit message: the old backlog traversal in mptcp_close_ssk() ran before __mptcp_close_ssk() took the ssk lock, holding neither the ssk lock nor mptcp_data_lock(). The race is a concurrent softirq RX path (subflow_data_ready() -> mptcp_data_ready() -> __mptcp_add_backlog(), under mptcp_data_lock()) adding to the backlog mid-traversal, not anything tied to a release_sock(ssk).
> - Added the missing Fixes tag (ee458a3f314e).

Thank you for the changelog. It is always useful to keep it in the note
section (under '---') to help reviewers.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2026-06-25  8:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  8:30 [PATCH net v4] mptcp: fix stale skb->sk reference on subflow close Kalpan Jani
2026-06-01  9:41 ` MPTCP CI
2026-06-25  6:40 ` Kalpan Jani
2026-06-25  8:06   ` Matthieu Baerts [this message]
2026-06-25  8:39 ` [PATCH " Matthieu Baerts
2026-06-26  9:14   ` Matthieu Baerts
2026-06-26 10:14     ` Kalpan Jani
2026-06-26 10:17       ` 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=ee4535dc-81e9-43a8-9b4c-e43be89e1628@kernel.org \
    --to=matttbe@kernel.org \
    --cc=akshit@mpiricsoftware.com \
    --cc=janak@mpiric.us \
    --cc=kalpan.jani@mpiricsoftware.com \
    --cc=kalpanjani009@gmail.com \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=shardul.b@mpiricsoftware.com \
    --cc=shardulsb08@gmail.com \
    --cc=syzkaller@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.