[PATCH] RISC-V: don't assume PI mutexes and robust futexes before 4.20 (bug 23864)

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[PATCH] RISC-V: don't assume PI mutexes and robust futexes before 4.20 (bug 23864)

Andreas Schwab
Support for futex_cmpxchg as only been added to 4.20-rc1.

Andreas.

        [BZ #23864]
        * sysdeps/unix/sysv/linux/riscv/kernel-features.h
        (__ASSUME_SET_ROBUST_LIST) [__LINUX_KERNEL_VERSION < 0x041400]:
        Undef.
---
 sysdeps/unix/sysv/linux/riscv/kernel-features.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/sysdeps/unix/sysv/linux/riscv/kernel-features.h b/sysdeps/unix/sysv/linux/riscv/kernel-features.h
index 37f4d99a92..d21c824624 100644
--- a/sysdeps/unix/sysv/linux/riscv/kernel-features.h
+++ b/sysdeps/unix/sysv/linux/riscv/kernel-features.h
@@ -21,3 +21,8 @@
 
 #undef __ASSUME_CLONE_DEFAULT
 #define __ASSUME_CLONE_BACKWARDS 1
+
+/* No support for PI mutexes or robust futexes before 4.20.  */
+#if __LINUX_KERNEL_VERSION < 0x041400
+# undef __ASSUME_SET_ROBUST_LIST
+#endif
--
2.19.1


--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH] RISC-V: don't assume PI mutexes and robust futexes before 4.20 (bug 23864)

DJ Delorie-2

Andreas Schwab <[hidden email]> writes:
> Support for futex_cmpxchg as only been added to 4.20-rc1.

I confirm it's not in 4.19.1.  I think it's safe to assume it will me in
4.20 official, so +1 from me.

Reviewed-by: DJ Delorie <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [PATCH] RISC-V: don't assume PI mutexes and robust futexes before 4.20 (bug 23864)

Palmer Dabbelt-2
On Tue, 06 Nov 2018 09:29:21 PST (-0800), [hidden email] wrote:
>
> Andreas Schwab <[hidden email]> writes:
>> Support for futex_cmpxchg as only been added to 4.20-rc1.
>
> I confirm it's not in 4.19.1.  I think it's safe to assume it will me in
> 4.20 official, so +1 from me.
>
> Reviewed-by: DJ Delorie <[hidden email]>

I agree, and I see it's already in.  Thanks!