From: Greg KH <gregkh@linuxfoundation.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, stable@vger.kernel.org,
Geliang Tang <tanggeliang@kylinos.cn>,
sashal@kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 6.1.y 1/3] mptcp: remove duplicate sk_reset_timer call
Date: Sun, 24 Aug 2025 09:11:31 +0200 [thread overview]
Message-ID: <2025082418-drier-exodus-1450@gregkh> (raw)
In-Reply-To: <20250822141124.49727-6-matttbe@kernel.org>
On Fri, Aug 22, 2025 at 04:11:26PM +0200, Matthieu Baerts (NGI0) wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> commit 5d13349472ac8abcbcb94407969aa0fdc2e1f1be upstream.
>
> sk_reset_timer() was called twice in mptcp_pm_alloc_anno_list.
>
> Simplify the code by using a 'goto' statement to eliminate the
> duplication.
>
> Note that this is not a fix, but it will help backporting the following
> patch. The same "Fixes" tag has been added for this reason.
>
> Fixes: 93f323b9cccc ("mptcp: add a new sysctl add_addr_timeout")
> Cc: stable@vger.kernel.org
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> Link: https://patch.msgid.link/20250815-net-mptcp-misc-fixes-6-17-rc2-v1-4-521fe9957892@kernel.org
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> [ Before commit e4c28e3d5c09 ("mptcp: pm: move generic PM helpers to
> pm.c"), mptcp_pm_alloc_anno_list() was in pm_netlink.c. The same patch
> can be applied there without conflicts. ]
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> ---
> net/mptcp/pm_netlink.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/net/mptcp/pm_netlink.c b/net/mptcp/pm_netlink.c
> index bb1a02e3dc3f..59d6e701d854 100644
> --- a/net/mptcp/pm_netlink.c
> +++ b/net/mptcp/pm_netlink.c
> @@ -383,9 +383,7 @@ bool mptcp_pm_alloc_anno_list(struct mptcp_sock *msk,
> if (WARN_ON_ONCE(mptcp_pm_is_kernel(msk)))
> return false;
>
> - sk_reset_timer(sk, &add_entry->add_timer,
> - jiffies + mptcp_get_add_addr_timeout(net));
> - return true;
> + goto reset_timer;
> }
>
> add_entry = kmalloc(sizeof(*add_entry), GFP_ATOMIC);
> @@ -399,6 +397,7 @@ bool mptcp_pm_alloc_anno_list(struct mptcp_sock *msk,
> add_entry->retrans_times = 0;
>
> timer_setup(&add_entry->add_timer, mptcp_pm_add_timer, 0);
> +reset_timer:
> sk_reset_timer(sk, &add_entry->add_timer,
> jiffies + mptcp_get_add_addr_timeout(net));
>
> --
> 2.50.0
>
>
Did not apply, something feels off here...
next prev parent reply other threads:[~2025-08-24 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 14:11 [PATCH 6.1.y 0/3] mptcp: fix recent failed backports (20250822) Matthieu Baerts (NGI0)
2025-08-22 14:11 ` [PATCH 6.1.y 1/3] mptcp: remove duplicate sk_reset_timer call Matthieu Baerts (NGI0)
2025-08-24 7:11 ` Greg KH [this message]
2025-08-22 14:11 ` [PATCH 6.1.y 2/3] mptcp: disable add_addr retransmission when timeout is 0 Matthieu Baerts (NGI0)
2025-08-22 14:11 ` [PATCH 6.1.y 3/3] selftests: mptcp: pm: check flush doesn't reset limits Matthieu Baerts (NGI0)
2025-08-24 7:11 ` Patch "selftests: mptcp: pm: check flush doesn't reset limits" has been added to the 6.1-stable tree gregkh
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=2025082418-drier-exodus-1450@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tanggeliang@kylinos.cn \
/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