OpenVZ / Virtuozzo kernel development (devel@openvz.org)
 help / color / mirror / Atom feed
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:13:37 +0100	[thread overview]
Message-ID: <179492841717.994824.3811650558054671884.b4-ty@b4> (raw)
In-Reply-To: <20261117074627.820727-1-eva.kurchatova@virtuozzo.com>

On Tue, 17 Nov 2026 09:44:50 +0200, Eva Kurchatova wrote:
> ms/mptcp: backport connection reset fixes
> 
> Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-155419
> 
> Matthieu Baerts (NGI0) (1):
>   ms/mptcp: avoid dup SUB_CLOSED events after disconnect
> 
> [...]

Applied to branch-rh10-6.12.0-211.75.1.26.x.vz10-ovz, will be released in rh10-6.12.0-211.75.1.24.3.vz10, thanks!

[1/2] ms/mptcp: reset msk state on early connect failure
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/daab25936d8c
[2/2] ms/mptcp: avoid dup SUB_CLOSED events after disconnect
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/26808dfbcd8c

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team


_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

      parent reply	other threads:[~2026-11-17 15:15 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 ` [Devel] [PATCH hci-8.1 0/2] ms/mptcp: backport connection reset fixes Konstantin Khorenko
2026-11-17 15:13 ` Konstantin Khorenko [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=179492841717.994824.3811650558054671884.b4-ty@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