From: Max Filippov Date: Wed, 30 Sep 2015 12:17:35 +0000 (+0300) Subject: xtensa: nommu: select HAVE_FUTEX_CMPXCHG X-Git-Tag: v4.14-rc1~3600^2~15^2~9 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d951ba21b95938c24a28a25295c44719d3b51ee2;p=platform%2Fkernel%2Flinux-rpi.git xtensa: nommu: select HAVE_FUTEX_CMPXCHG Not having HAVE_FUTEX_CMPXCHG makes futex_detect_cmpxchg probe cmpxchg_futex_value_locked with NULL address. It's not guaranteed to fault without MMU, instead it locks up on Xtensa when there's no RAM at address 0. Select HAVE_FUTEX_CMPXCHG in noMMU Xtensa configurations. Signed-off-by: Max Filippov --- diff --git a/arch/xtensa/Kconfig b/arch/xtensa/Kconfig index 366a981..3d35867 100644 --- a/arch/xtensa/Kconfig +++ b/arch/xtensa/Kconfig @@ -17,6 +17,7 @@ config XTENSA select HAVE_DMA_API_DEBUG select HAVE_DMA_ATTRS select HAVE_FUNCTION_TRACER + select HAVE_FUTEX_CMPXCHG if !MMU select HAVE_IRQ_TIME_ACCOUNTING select HAVE_OPROFILE select HAVE_PERF_EVENTS