[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260114113243-e5b1436b-1729-44ad-aa9e-57886bde6660@linutronix.de>
Date: Wed, 14 Jan 2026 11:35:07 +0100
From: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
To: sun jian <sun.jian.kdev@...il.com>
Cc: Andy Lutomirski <luto@...nel.org>, Thomas Gleixner <tglx@...nel.org>,
Vincenzo Frascino <vincenzo.frascino@....com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lib/vdso: guard clockid before building u32 bitmask
On Wed, Jan 14, 2026 at 06:26:17PM +0800, sun jian wrote:
> On Wed, Jan 14, 2026 at 5:53 PM Thomas Weißschuh
> <thomas.weissschuh@...utronix.de> wrote:
> > On which specific kernel commit are you?
> I'm on:
> b71e635feefc852405b14620a7fc58c4c80c0f73
> ("Merge tag 'cgroup-for-6.19-rc5-fixes'")
> , no tags available.
> > The message points to '} else if (msg & VDSO_AUX) {'. This means that it probably
> > complains about the shift in '#define VDSO_AUX __GENMASK(CLOCK_AUX_LAST, CLOCK_AUX)'.
> > We had problems in that area before, so I'd like to get all the details.
> >
> > Which sparse version are you using?
> Sparse version:
>
> v0.6.4-73-gfbdde312
>
> The warning was reproduced with gcc + CHECK=sparse on x86, via the vdso32
> include path (arch/x86/entry/vdso/vdso32/vclock_gettime.c).
I was able to reproduce the warning. It is a false positive due to the way
sparse is configured. The 32-bit compat vDSO is using the 64-bit sparse flags.
See also:
https://lore.kernel.org/lkml/20251107155158-90fb8c9c-59bf-47b3-8756-7c406166db70@linutronix.de/
Thomas
Powered by blists - more mailing lists