x86/vdso: Fix latent bug in vclock_pages calculation

Browse source

The vclock pages are *after* the non-vclock pages. Currently there are both
two vclock and two non-vclock pages so the existing logic works by
accident.  As soon as the number of pages changes it will break however.
This will be the case with the introduction of the generic vDSO data
storage.

Use a macro to keep the calculation understandable and in sync between
the linker script and mapping code.

Fixes: e93d2521b2 ("x86/vdso: Split virtual clock pages into dedicated mapping")
Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/all/20250204-vdso-store-rng-v3-1-13a4669dfc8c@linutronix.de

...

This commit is contained in:

Thomas Weißschuh 2025-02-04 13:05:33 +01:00 • committed by Thomas Gleixner

parent a64dcfb451

commit 3ef32d90cd

3 changed files with 3 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

arch/x86/entry/vdso/vdso-layout.lds.S

View file

2

arch/x86/entry/vdso/vma.c

View file

1

arch/x86/include/asm/vdso/vsyscall.h

View file