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 mainline fixes
Date: Mon, 16 Nov 2026 18:03:48 +0100 [thread overview]
Message-ID: <179484862846.861498.15938141204939049807.b4-review@b4> (raw)
In-Reply-To: <20261116145652.625598-1-eva.kurchatova@virtuozzo.com>
Applying as is.
On Mon, 16 Nov 2026 16:43:01 +0200, Eva Kurchatova <eva.kurchatova@virtuozzo.com> wrote:
> Paolo Abeni (2):
> ms/mptcp: do not reschedule the RTX timer for fallback sockets
> ms/mptcp: fix subflow bitfield misuse
Separate patches, not needed for this series. I created a task:
1. Two mainline fixes that go with these are missing here:
29afe67082b2 ("mptcp: reset msk state on early connect failure"),
patch 1 of the series 2/2 comes from: after an early fallback and
a failed subflow connect the next connect() or listen() sets
MPTCP_RTX_ENABLED again and nothing clears it. And 280d654324e3
("mptcp: avoid dup SUB_CLOSED events after disconnect"), another
fix of d82809b6c5f2. 85c580b0d859 is already in VSTOR-155322.
https://virtuozzo.atlassian.net/browse/VSTOR-155419
--
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-16 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 14:43 Eva Kurchatova
2026-11-16 14:43 ` [Devel] [PATCH hci-8.1 1/2] ms/mptcp: do not reschedule the RTX timer for fallback sockets Eva Kurchatova
2026-11-16 15:02 ` no-reply
2026-11-16 14:43 ` [Devel] [PATCH hci-8.1 2/2] ms/mptcp: fix subflow bitfield misuse Eva Kurchatova
2026-11-16 15:00 ` no-reply
2026-11-16 17:03 ` Konstantin Khorenko [this message]
2026-11-16 17:04 ` [Devel] [PATCH hci-8.1 0/2] ms/mptcp: backport mainline 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=179484862846.861498.15938141204939049807.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox