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 v2 0/5] ms/eventfs: fix kernel panic on NULL dereference
Date: Thu, 12 Nov 2026 17:50:46 +0100	[thread overview]
Message-ID: <179450224606.4060562.12978390397560541359.b4-ty@b4> (raw)
In-Reply-To: <20261112000926.381308-2-eva.kurchatova@virtuozzo.com>

On Thu, 12 Nov 2026 02:07:52 +0200, Eva Kurchatova wrote:
> ms/eventfs: fix kernel panic on NULL dereference
> 
> Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-154529
> 
> Note: Two of the patches are cherry-picks from 6.12.y stable tree
> backport, as the code differs in the mainline.
> 
> [...]

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

[1/5] ms/eventfs: Hold eventfs_mutex and SRCU when remount walks events
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/5c4a6a9742ee
[2/5] ms/eventfs: Fix use-after-free in eventfs_remove_rec()
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/f964cc4ac71a
[3/5] ms/eventfs: Initialize ei->children and ei->list in init_ei()
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/d5a703a52eb1
[4/5] ms/eventfs: Use children field for rcu head and add memory barriers
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/f7e44a71e469
[5/5] ms/eventfs: fix SRCU read lock leak in eventfs_iterate()
      https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/3751e32064ff

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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  0:07 Eva Kurchatova
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 1/5] ms/eventfs: Hold eventfs_mutex and SRCU when remount walks events Eva Kurchatova
2026-11-12  0:15   ` no-reply
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 2/5] ms/eventfs: Fix use-after-free in eventfs_remove_rec() Eva Kurchatova
2026-11-12  0:13   ` no-reply
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 3/5] ms/eventfs: Use children field for rcu head and add memory barriers Eva Kurchatova
2026-11-12  0:16   ` no-reply
2026-11-12  4:18     ` Eva Kurchatova (Virtuozzo)
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 4/5] ms/eventfs: fix SRCU read lock leak in eventfs_iterate() Eva Kurchatova
2026-11-12  0:15   ` no-reply
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12  0:07 ` [Devel] [PATCH hci-8.1 v2 5/5] ms/eventfs: Initialize ei->children and ei->list in init_ei() Eva Kurchatova
2026-11-12  0:16   ` no-reply
2026-11-12 16:43   ` Konstantin Khorenko
2026-11-12 16:43 ` [Devel] [PATCH hci-8.1 v2 0/5] ms/eventfs: fix kernel panic on NULL dereference Konstantin Khorenko
2026-11-12 16:50 ` 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=179450224606.4060562.12978390397560541359.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