[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171030141813.nozm5bgumb5qp2ol@lakrids.cambridge.arm.com>
Date: Mon, 30 Oct 2017 14:18:14 +0000
From: Mark Rutland <mark.rutland@....com>
To: Mark Salyzyn <salyzyn@...roid.com>
Cc: linux-kernel@...r.kernel.org, James Morse <james.morse@....com>,
Russell King <linux@...linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Andy Lutomirski <luto@...capital.net>,
Dmitry Safonov <dsafonov@...tuozzo.com>,
John Stultz <john.stultz@...aro.org>,
Laura Abbott <labbott@...hat.com>,
Kees Cook <keescook@...omium.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Andy Gross <andy.gross@...aro.org>,
Kevin Brodsky <kevin.brodsky@....com>,
Andrew Pinski <apinski@...ium.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 0/12] arm+arm64: vdso unification to lib/vdso/
Hi,
On Fri, Oct 27, 2017 at 03:23:48PM -0700, Mark Salyzyn wrote:
> Note I noticed a bug in the old implementation of __kernel_clock_getres;
> it was checking only the lower 32bits of the pointer; this would work
> for most cases but could fail in a few.
Sorry if this is a stupid question, but do you mean from a prior version
of this series, or the one in the kernel today?
Thanks,
Mark.
Powered by blists - more mailing lists