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/fs: backport RCU pathwalk UAF fixes
Date: Tue, 17 Nov 2026 16:15:37 +0100	[thread overview]
Message-ID: <179492853743.994824.11197441297883973475.b4-review@b4> (raw)
In-Reply-To: <20261117055330.810827-1-eva.kurchatova@virtuozzo.com>

Applying as is.

On Tue, 17 Nov 2026 07:52:11 +0200, Eva Kurchatova wrote:
> Christian Brauner (2):
>   ms/ext4: free the sbi after a grace period
>   ms/unicode: free the map after a grace period

Both are the 6.12.y commits; the ext4 one rightly leaves out the KUnit
hunks. Note that 2/2 compiles to nothing in our kernels, CONFIG_UNICODE
is not set; it is fine to keep it for parity with 6.12.y.

Separate patches, not needed for this series; I created a task for
each:

1. Patch 5 of the same upstream series, f0e48172a59e5 ("ipc: drop the
   mqueue mount with kern_unmount() on setup failure"), with
   7229d74e5e8c1 before it: create_ipc_ns() here never drops
   ns->mq_mnt when it fails after mq_init_ns(), so the mqueue mount
   leaks on a failed CT start or unshare(CLONE_NEWIPC).
   https://virtuozzo.atlassian.net/browse/VSTOR-155528

2. 496bb99b7e66f ("ext4: fix the might_sleep() warnings in kvfree()"),
   de009e11f31a8 in 6.12.y: ext4_group_desc_free() and
   ext4_flex_groups_free() still call kvfree() under rcu_read_lock().
   https://virtuozzo.atlassian.net/browse/VSTOR-155529

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 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  5:52 Eva Kurchatova
2026-11-17  5:52 ` [Devel] [PATCH hci-8.1 1/2] ms/ext4: free the sbi after a grace period Eva Kurchatova
2026-11-17  6:02   ` no-reply
2026-11-17  5:52 ` [Devel] [PATCH hci-8.1 2/2] ms/unicode: free the map " Eva Kurchatova
2026-11-17  5:59   ` no-reply
2026-11-17 15:15 ` Konstantin Khorenko [this message]
2026-11-17 15:15 ` [Devel] [PATCH hci-8.1 0/2] ms/fs: backport RCU pathwalk UAF 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=179492853743.994824.11197441297883973475.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