public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Arnd Bergmann" <arnd@arndb.de>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, Russell King <linux@armlinux.org.uk>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christophe Leroy <chleroy@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH 1/7] x86/vdso: Respect COMPAT_32BIT_TIME
Date: Tue, 3 Mar 2026 13:36:52 -0800	[thread overview]
Message-ID: <0d2d834d-0f3c-43bb-9530-da6c2492763a@zytor.com> (raw)
In-Reply-To: <d92f424c-9aee-417e-899e-3a0002a80f4a@app.fastmail.com>

On 2026-03-03 13:27, Arnd Bergmann wrote:
> 
> I see. I would argue here that a link failure is actually the best
> case then: the entire point of CONFIG_COMPAT_32BIT_TIME=n is to
> enforce the fail-early case, as opposed to silent data corruption
> after (now) 12 years of operation.
> 
> I don't think there is an actual link failure here, as dl_vdso_vsym()
> resolves it at runtime by glibc (when using time32), while musl
> doesn't use __vdso_gettimeofday at all.
> 

Well, the former is a link failure -- just one handled reasonably gracefully.
A library that really wants a fallback can presumably also avoid the problem
by provide a weak reference for the fallback.

	-hpa



  reply	other threads:[~2026-03-03 21:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  6:57 [PATCH 0/7] vDSO: Respect COMPAT_32BIT_TIME Thomas Weißschuh
2026-02-27  6:57 ` [PATCH 1/7] x86/vdso: " Thomas Weißschuh
2026-02-27  8:51   ` Arnd Bergmann
2026-02-27  8:58     ` Arnd Bergmann
2026-02-27  9:34       ` Thomas Weißschuh
2026-03-03 18:11         ` H. Peter Anvin
2026-03-03 20:50           ` Arnd Bergmann
2026-03-03 21:00             ` H. Peter Anvin
2026-03-03 21:27               ` Arnd Bergmann
2026-03-03 21:36                 ` H. Peter Anvin [this message]
2026-04-10  7:24             ` Thomas Weißschuh
2026-04-13 15:59               ` Arnd Bergmann
2026-04-13 16:13                 ` Thomas Weißschuh
2026-04-13 16:57                   ` Arnd Bergmann
2026-04-14 10:16                     ` Thomas Weißschuh
2026-03-04  7:35           ` Thomas Weißschuh
2026-03-04 18:30             ` H. Peter Anvin
2026-03-05  9:24               ` Thomas Weißschuh
2026-03-05 23:57                 ` H. Peter Anvin
2026-03-06  9:42                   ` Thomas Weißschuh
2026-03-06 20:52                     ` H. Peter Anvin
2026-02-27  6:57 ` [PATCH 2/7] ARM: VDSO: " Thomas Weißschuh
2026-02-27  6:57 ` [PATCH 3/7] arm64: vdso32: " Thomas Weißschuh
2026-02-27  6:57 ` [PATCH 4/7] powerpc/vdso: " Thomas Weißschuh
2026-02-27  6:57 ` [PATCH 5/7] MIPS: VDSO: Drop kconfig MIPS_CLOCK_VSYSCALL Thomas Weißschuh
2026-02-27  8:46   ` Arnd Bergmann
2026-02-27  9:31     ` Thomas Weißschuh
2026-02-27 10:03       ` Arnd Bergmann
2026-02-27 10:17         ` Thomas Weißschuh
2026-02-27  6:57 ` [PATCH 6/7] MIPS: VDSO: Respect COMPAT_32BIT_TIME Thomas Weißschuh
2026-02-27  6:57 ` [PATCH 7/7] vdso/gettimeofday: Verify COMPAT_32BIT_TIME interactions Thomas Weißschuh
2026-02-27  8:49   ` Arnd Bergmann

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=0d2d834d-0f3c-43bb-9530-da6c2492763a@zytor.com \
    --to=hpa@zytor.com \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=chleroy@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luto@kernel.org \
    --cc=maddy@linux.ibm.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=tglx@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=tsbogend@alpha.franken.de \
    --cc=vincenzo.frascino@arm.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    /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