From: no-reply@sashiko.virtuozzo.com
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>, khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2 2/6] ms/vdso/timens: Move functions to new file
Date: Mon, 19 Oct 2026 00:12:12 +0000 [thread overview]
Message-ID: <010701a1518067d5-c519f507-7936-43bf-88ce-84449aba0484-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261019000649.1371025-3-eva.kurchatova@virtuozzo.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] timens: stale extern offset_lock left in time_namespace.h after rename
--
commit 10270c644c766f4ad4754e8bd546e29088de7a79
Author: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
ms/vdso/timens: Move functions to new file
This commit moves the glue functions between time namespaces and the vDSO
into a new file, kernel/time/namespace_vdso.c. It renames offset_lock to
timens_offset_lock, declared in a new private header, and converts the
mutex and mmap_read_lock() users to guard().
Link: https://patch.msgid.link/20260326-vdso-timens-decoupling-v2-1-c82693a7775f@linutronix.de
> diff --git a/include/linux/time_namespace.h b/include/linux/time_namespace.h
> index 3d3b529c5a98b..23384eafebfb5 100644
> --- a/include/linux/time_namespace.h
> +++ b/include/linux/time_namespace.h
> @@ -35,8 +35,6 @@ extern struct time_namespace init_time_ns;
> extern struct mutex offset_lock;
[Severity: Low]
This isn't a bug, but is this declaration now stale?
The mutex is renamed to timens_offset_lock, defined in
kernel/time/namespace.c:
DEFINE_MUTEX(timens_offset_lock);
and declared in the new private header namespace_internal.h:
extern struct mutex timens_offset_lock;
Nothing defines or references offset_lock any more, but this public
declaration is left in include/linux/time_namespace.h, while the
vdso_join_timens() declarations just below it were removed.
Should "extern struct mutex offset_lock;" be dropped from the header as well?
>
> #ifdef CONFIG_TIME_NS
> -extern int vdso_join_timens(struct task_struct *task,
> - struct time_namespace *ns);
> extern void timens_commit(struct task_struct *tsk, struct time_namespace *ns);
[ ... ]
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261019000649.1371025-1-eva.kurchatova@virtuozzo.com?part=2
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-10-19 0:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 0:05 [Devel] [PATCH hci-8.1 v2 0/6] timens: Remove dependency on the vDSO Eva Kurchatova
2026-10-19 0:05 ` [Devel] [PATCH hci-8.1 v2 1/6] ms/vdso: Drop Kconfig GENERIC_VDSO_TIME_NS Eva Kurchatova
2026-10-19 0:12 ` no-reply
2026-10-19 0:05 ` [Devel] [PATCH hci-8.1 v2 2/6] ms/vdso/timens: Move functions to new file Eva Kurchatova
2026-10-19 0:12 ` no-reply [this message]
2026-10-19 0:05 ` [Devel] [PATCH hci-8.1 v2 3/6] ms/timens: Remove dependency on the vDSO Eva Kurchatova
2026-10-19 0:15 ` no-reply
2026-10-19 0:05 ` [Devel] [PATCH hci-8.1 v2 4/6] timens: freeze the offsets on the first join without the vDSO too Eva Kurchatova
2026-10-19 0:14 ` no-reply
2026-10-19 0:05 ` [Devel] [PATCH hci-8.1 v2 5/6] timens: keep the option off where the vDSO updates its own time data Eva Kurchatova
2026-10-19 0:16 ` no-reply
2026-10-19 0:05 ` [Devel] [PATCH hci-8.1 v2 6/6] config: follow the TIME_NS Kconfig change in config.vz10.minimal Eva Kurchatova
2026-10-19 0:16 ` 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=010701a1518067d5-c519f507-7936-43bf-88ce-84449aba0484-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@virtuozzo.com \
--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 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.