From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 0/4] ms/eventfs: fix kernel panic on NULL dereference
Date: Wed, 11 Nov 2026 22:34:16 +0200 [thread overview]
Message-ID: <20261111203529.363554-1-eva.kurchatova@virtuozzo.com> (raw)
Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-154529
Note: The last two patches are cherry-picks from 6.12.y stable tree
backport, as the code differs in the mainline.
Deepanshu Kartikey (1):
ms/eventfs: Initialize ei->children and ei->list in init_ei()
Joseph Qi (1):
ms/eventfs: fix SRCU read lock leak in eventfs_iterate()
Shuangpeng Bai (1):
ms/eventfs: Fix use-after-free in eventfs_remove_rec()
Steven Rostedt (1):
ms/eventfs: Use children field for rcu head and add memory barriers
fs/tracefs/event_inode.c | 37 ++++++++++++++++++++++++++++++-------
fs/tracefs/internal.h | 4 ++--
2 files changed, 32 insertions(+), 9 deletions(-)
--
2.56.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-11-11 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 20:34 Eva Kurchatova [this message]
2026-11-11 20:34 ` [Devel] [PATCH hci-8.1 1/4] ms/eventfs: Fix use-after-free in eventfs_remove_rec() Eva Kurchatova
2026-11-11 20:39 ` no-reply
2026-11-11 20:34 ` [Devel] [PATCH hci-8.1 2/4] ms/eventfs: Use children field for rcu head and add memory barriers Eva Kurchatova
2026-11-11 20:40 ` no-reply
2026-11-11 20:34 ` [Devel] [PATCH hci-8.1 3/4] ms/eventfs: fix SRCU read lock leak in eventfs_iterate() Eva Kurchatova
2026-11-11 20:39 ` no-reply
2026-11-11 20:34 ` [Devel] [PATCH hci-8.1 4/4] ms/eventfs: Initialize ei->children and ei->list in init_ei() Eva Kurchatova
2026-11-11 20:40 ` no-reply
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=20261111203529.363554-1-eva.kurchatova@virtuozzo.com \
--to=eva.kurchatova@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@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