This is the mail archive of the
mailing list for the glibc project.
Re: Should Linux VDSO be using symbol version based on the released kernel?
- From: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- To: libc-alpha at sourceware dot org
- Date: Wed, 4 May 2016 15:22:08 -0300
- Subject: Re: Should Linux VDSO be using symbol version based on the released kernel?
- Authentication-results: sourceware.org; auth=none
- References: <572A252D dot 8030204 at redhat dot com>
On 04/05/2016 13:37, Carlos O'Donell wrote:
> The Linux VDSO uses a singular version string, different by
> architecture, for all VDSO symbols e.g. LINUX_2.6.29 for s390x.
> Should the Linux kernel be using LINUX_4.5 as the version string
> for new VDSO symbols added in LINUX_4.5?
> That way we can talk sensibly about what VDSO symbols were added
> upstream, and talk sensible about the ABI/API being exported by
> any given kernel via the VDSO?
> Right now the version is really only meaningless version for
> future compat support.
Ideally I would say yes, however the way we use the vDSO is not
by exporting it directly in GLIBC own supported versions, but
rather through wrappers and these already take care of check if
the symbol exist based on exported kernel version.
And I do not think we should think the vDSO as an stable ABI
that we must enforce symbol version compatibility, but rather
helper functions that GLIBC would use internally.
It is the same rationale based on other Linux exported facilities
that we do support directly.