From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v5 1/5] timens: make offset_lock private to namespace.c again
Date: Wed, 21 Oct 2026 07:08:39 +0300 [thread overview]
Message-ID: <20261021040939.2103947-2-eva.kurchatova@virtuozzo.com> (raw)
In-Reply-To: <20261021040939.2103947-1-eva.kurchatova@virtuozzo.com>
51a228b021a0 ("ve: Add interface for ve::clock_[monotonic|bootbased]
adjustment") exported the lock for the ve code, and nothing took it
up, then or since: the only users are in namespace.c. Put it back the
way mainline has it, so that the mainline changes to this file apply
as they are.
https://virtuozzo.atlassian.net/browse/VSTOR-148112
Feature: fix ms/timens
Signed-off-by: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
---
include/linux/time_namespace.h | 2 --
kernel/time/namespace.c | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/include/linux/time_namespace.h b/include/linux/time_namespace.h
index 3d3b529c5a98..bb2c52f4fc94 100644
--- a/include/linux/time_namespace.h
+++ b/include/linux/time_namespace.h
@@ -32,8 +32,6 @@ struct time_namespace {
extern struct time_namespace init_time_ns;
-extern struct mutex offset_lock;
-
#ifdef CONFIG_TIME_NS
extern int vdso_join_timens(struct task_struct *task,
struct time_namespace *ns);
diff --git a/kernel/time/namespace.c b/kernel/time/namespace.c
index e85f947d4063..e3642278df43 100644
--- a/kernel/time/namespace.c
+++ b/kernel/time/namespace.c
@@ -214,7 +214,7 @@ struct page *find_timens_vvar_page(struct vm_area_struct *vma)
* Protects possibly multiple offsets writers racing each other
* and tasks entering the namespace.
*/
-DEFINE_MUTEX(offset_lock);
+static DEFINE_MUTEX(offset_lock);
static void timens_set_vvar_page(struct task_struct *task,
struct time_namespace *ns)
--
2.56.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-10-21 4:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 4:08 [Devel] [PATCH hci-8.1 v5 0/5] timens: Remove dependency on the vDSO Eva Kurchatova
2026-10-21 4:08 ` Eva Kurchatova [this message]
2026-10-21 4:13 ` [Devel] [PATCH hci-8.1 v5 1/5] timens: make offset_lock private to namespace.c again no-reply
2026-10-21 4:08 ` [Devel] [PATCH hci-8.1 v5 2/5] ms/vdso: Drop Kconfig GENERIC_VDSO_TIME_NS Eva Kurchatova
2026-10-21 4:14 ` no-reply
2026-10-21 4:26 ` Eva Kurchatova (Virtuozzo)
2026-10-21 4:08 ` [Devel] [PATCH hci-8.1 v5 3/5] ms/vdso/timens: Move functions to new file Eva Kurchatova
2026-10-21 4:15 ` no-reply
2026-10-21 4:08 ` [Devel] [PATCH hci-8.1 v5 4/5] ms/timens: Remove dependency on the vDSO Eva Kurchatova
2026-10-21 4:16 ` no-reply
2026-10-21 4:24 ` Eva Kurchatova (Virtuozzo)
2026-10-21 4:08 ` [Devel] [PATCH hci-8.1 v5 5/5] config: follow the TIME_NS Kconfig change in config.vz10.minimal Eva Kurchatova
2026-10-21 4:16 ` no-reply
2026-10-21 4:19 ` [Devel] [PATCH hci-8.1 v5 0/5] timens: Remove dependency on the vDSO Eva Kurchatova (Virtuozzo)
2026-10-21 12:29 ` 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=20261021040939.2103947-2-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