Stable Archive on lore.kernel.org
 help / color / Atom feed
* Backport request: arm-8987-1-vdso-fix-incorrect-clock_gettime64.patch
@ 2020-10-16  9:39 Rui Salvaterra
  2020-10-16  9:53 ` Greg KH
  0 siblings, 1 reply; 3+ messages in thread
From: Rui Salvaterra @ 2020-10-16  9:39 UTC (permalink / raw)
  To: gregkh; +Cc: stable, jaedon.shin

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=linux-5.3.y&id=22ca962288c0a1c9729e8e440b9bb9ad05df6db6

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Backport request: arm-8987-1-vdso-fix-incorrect-clock_gettime64.patch
  2020-10-16  9:39 Backport request: arm-8987-1-vdso-fix-incorrect-clock_gettime64.patch Rui Salvaterra
@ 2020-10-16  9:53 ` Greg KH
  2020-10-16 11:00   ` Rui Salvaterra
  0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2020-10-16  9:53 UTC (permalink / raw)
  To: Rui Salvaterra; +Cc: stable, jaedon.shin

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Backport request: arm-8987-1-vdso-fix-incorrect-clock_gettime64.patch
  2020-10-16  9:53 ` Greg KH
@ 2020-10-16 11:00   ` Rui Salvaterra
  0 siblings, 0 replies; 3+ messages in thread
From: Rui Salvaterra @ 2020-10-16 11:00 UTC (permalink / raw)
  To: Greg KH; +Cc: stable, jaedon.shin

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=4486c579cbf0d989080705f515d08cb48636ba88
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/vdso?id=74d06efb9c2f99b496eb118b1e941dc4c6404e93

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-16  9:39 Backport request: arm-8987-1-vdso-fix-incorrect-clock_gettime64.patch Rui Salvaterra
2020-10-16  9:53 ` Greg KH
2020-10-16 11:00   ` Rui Salvaterra

Stable Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://lore.kernel.org/stable \
		stable@vger.kernel.org
	public-inbox-index stable

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git