From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 0/2] ms/mptcp: backport connection reset fixes
Date: Tue, 17 Nov 2026 16:12:55 +0100 [thread overview]
Message-ID: <179492837537.994824.225069300559225292.b4-review@b4> (raw)
In-Reply-To: <20261117074627.820727-1-eva.kurchatova@virtuozzo.com>
Applying as is.
On Tue, 17 Nov 2026 09:44:50 +0200, Eva Kurchatova wrote:
> Matthieu Baerts (NGI0) (1):
> ms/mptcp: avoid dup SUB_CLOSED events after disconnect
>
> Quanye Yang (1):
> ms/mptcp: reset msk state on early connect failure
Both are the 6.12.y commits, and both bugs are reachable here. The
series does not overlap with the stability and cc-stable series and
can go in at any point.
Separate patches, not needed for this series; I created a task:
1. Three more Cc stable fixes from the same upstream postings are
missing: c9c90cf437a9e ("mptcp: hold MP_JOIN msk ref when cloning
reqsk"), 2093bc7fa5005 ("mptcp: fix MP_CAPABLE token migration when
cloning reqsk") and dccf46179ddd6 ("mptcp: only reset subflow
errors when propagated").
https://virtuozzo.atlassian.net/browse/VSTOR-155530
Thanks.
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-11-17 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 7:44 Eva Kurchatova
2026-11-17 7:44 ` [Devel] [PATCH hci-8.1 1/2] ms/mptcp: reset msk state on early connect failure Eva Kurchatova
2026-11-17 7:51 ` no-reply
2026-11-17 7:44 ` [Devel] [PATCH hci-8.1 2/2] ms/mptcp: avoid dup SUB_CLOSED events after disconnect Eva Kurchatova
2026-11-17 7:51 ` no-reply
2026-11-17 15:12 ` Konstantin Khorenko [this message]
2026-11-17 15:13 ` [Devel] [PATCH hci-8.1 0/2] ms/mptcp: backport connection reset fixes Konstantin Khorenko
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=179492837537.994824.225069300559225292.b4-review@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@virtuozzo.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.