All Virtuozzo development lists (kernel + QEMU)
 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/4] ms/mptcp: backport cc-stable fixes
Date: Tue, 17 Nov 2026 12:29:43 +0100	[thread overview]
Message-ID: <179491498385.113083.8710612646167447943.b4-review@b4> (raw)
In-Reply-To: <20261116180419.685520-3-eva.kurchatova@virtuozzo.com>

I won't apply this version, please send v2 with the changes below.

On Mon, 16 Nov 2026 20:03:00 +0200, Eva Kurchatova wrote:
> Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-15532

The backports are right: 3/4 and 4/4 are mainline as is, and the 2/4
timer adaptation matches __mptcp_init_sock() here and the 6.12.y
backport. What to change for v2:

1. Base v2 on "ms/mptcp: stability fixes" (v4 when it comes). Its
   7/11 is 2834f8edd74d5 ("mptcp: cleanup fallback dummy mapping
   generation"), the commit 1/4 goes with in mainline and in 6.12.y,
   where it was taken as "Stable-dep-of: 0981f90e1a05". Today the two
   series do not apply on top of each other (both add a line after
   msk->fastclosing = 0 in mptcp_disconnect()). On that base 1/4 is a
   plain cherry-pick and needs no rebase note.

2. Patch 2: the rebase note names e4141ea18a73, the 6.12.y id; the
   mainline commit is 08dfe370239e5.

3. Cover letter: the task is VSTOR-155322. Say what the four fixes
   fix, how the series was tested, and that it goes on top of the
   stability series.

Thanks.

-- 
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 11:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 18:03 Eva Kurchatova
2026-11-16 18:03 ` [Devel] [PATCH hci-8.1 1/4] ms/mptcp: reset rcv wnd on disconnect Eva Kurchatova
2026-11-16 18:09   ` no-reply
2026-11-17 11:29   ` Konstantin Khorenko
2026-11-16 18:03 ` [Devel] [PATCH hci-8.1 2/4] ms/mptcp: prevent race between disconnect() and rtx Eva Kurchatova
2026-11-16 18:08   ` no-reply
2026-11-17 11:29   ` Konstantin Khorenko
2026-11-16 18:03 ` [Devel] [PATCH hci-8.1 3/4] ms/mptcp: close race between scheduler and state change Eva Kurchatova
2026-11-16 18:10   ` no-reply
2026-11-16 18:03 ` [Devel] [PATCH hci-8.1 4/4] ms/mptcp: fix bad accounting in __mptcp_subflow_push_pending() Eva Kurchatova
2026-11-16 18:10   ` no-reply
2026-11-17 11:29 ` 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=179491498385.113083.8710612646167447943.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.