[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260114105027-b158ddd9-abba-48cf-b4b2-51589002f129@linutronix.de>
Date: Wed, 14 Jan 2026 10:53:20 +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 05:31:48PM +0800, sun jian wrote:
> On Wed, Jan 14, 2026 at 4:56 PM Thomas Weißschuh
> <thomas.weissschuh@...utronix.de> wrote:
> > So this looks like a false-positive. Can you post the sparse warning?
> Here is the sparse warning I saw:
>
> arch/x86/entry/vdso/vdso32/../../../../../lib/vdso/gettimeofday.c:454:26:
> warning: shift too big (40) for type unsigned long
>
> It is emitted when checking the vdso32 include path via vclock_gettime.c.
On which specific kernel commit are you?
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?
(...)
Thomas
Powered by blists - more mailing lists