Hi, Greg,
I see the arm-8987-1-vdso-fix-incorrect-clock_gettime64.patch ("ARM: 8987/1: VDSO: Fix incorrect clock_gettime64") has been applied to the 5.7-stable tree [1], but this should have been applied to 5.3+, since it's the first version to contain the commit this patch fixes [2].
Thanks in advance, Rui
[1] https://marc.info/?l=linux-stable-commits&m=159628776730078&w=2 [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=l...
On Fri, Oct 16, 2020 at 10:39:50AM +0100, Rui Salvaterra wrote:
Hi, Greg,
I see the arm-8987-1-vdso-fix-incorrect-clock_gettime64.patch ("ARM: 8987/1: VDSO: Fix incorrect clock_gettime64") has been applied to the 5.7-stable tree [1], but this should have been applied to 5.3+, since it's the first version to contain the commit this patch fixes [2].
But that's not what that commit says should happen, it says it fixes a commit that showed up in the 5.5 release.
Is it incorrect? Have you tested this on 5.4.y?
thanks,
greg k-h
Hi, Greg,
On Fri, 16 Oct 2020 at 10:52, Greg KH gregkh@linuxfoundation.org wrote:
But that's not what that commit says should happen, it says it fixes a commit that showed up in the 5.5 release.
Is it incorrect? Have you tested this on 5.4.y?
Well, this took quite a lot of digging, sorry for the delay (I'm definitely not a timers/vDSO expert, I was just trying to understand the reason for a strange Musl workaround [1]), but you're completely right. Only 5.5+ is affected, since it was at that time the clock_gettime64 entry point was introduced for ARM [2]. Sorry for the noise!
Thanks, Rui
[1] https://git.musl-libc.org/cgit/musl/commit/?id=4486c579cbf0d989080705f515d08... [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ar...
linux-stable-mirror@lists.linaro.org
-
Greg KH -
Rui Salvaterra