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/eventfs: RCU handling fixes
Date: Mon, 16 Nov 2026 18:02:38 +0100 [thread overview]
Message-ID: <179484855821.861498.11747294956957453457.b4-ty@b4> (raw)
In-Reply-To: <20261116144143.624802-1-eva.kurchatova@virtuozzo.com>
On Mon, 16 Nov 2026 16:40:22 +0200, Eva Kurchatova wrote:
> ms/eventfs: RCU handling fixes
>
> Patchset for tasks:
> - https://virtuozzo.atlassian.net/browse/VSTOR-154849
> - https://virtuozzo.atlassian.net/browse/VSTOR-154848
>
> Rebased backports from mainline only.
>
> [...]
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/eventfs: Use list_add_tail_rcu() for SRCU-protected children list
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/6e3daa6c0201
[2/2] ms/eventfs: Free the eventfs_inode after an rcu grace period too
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/18bd29edd62f
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-11-16 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 14:40 Eva Kurchatova
2026-11-16 14:40 ` [Devel] [PATCH hci-8.1 1/2] ms/eventfs: Use list_add_tail_rcu() for SRCU-protected children list Eva Kurchatova
2026-11-16 14:45 ` no-reply
2026-11-16 14:40 ` [Devel] [PATCH hci-8.1 2/2] ms/eventfs: Free the eventfs_inode after an rcu grace period too Eva Kurchatova
2026-11-16 14:45 ` no-reply
2026-11-16 17:02 ` [Devel] [PATCH hci-8.1 0/2] ms/eventfs: RCU handling fixes Konstantin Khorenko
2026-11-16 17:02 ` 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=179484855821.861498.11747294956957453457.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 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.