aboutsummaryrefslogtreecommitdiffstats
path: root/arch/mips/Kconfig
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2019-01-10 17:24:31 +0100
committerPaul Burton <paul.burton@mips.com>2019-01-11 11:23:58 -0800
commit5a9372f751b5350e0ce3d2ee91832f1feae2c2e5 (patch)
treeb405c318cc8d8654857045a255cac16b48964515 /arch/mips/Kconfig
parentDisable MSI also when pcie-octeon.pcie_disable on (diff)
downloadlinux-dev-5a9372f751b5350e0ce3d2ee91832f1feae2c2e5.tar.xz
linux-dev-5a9372f751b5350e0ce3d2ee91832f1feae2c2e5.zip
mips: fix n32 compat_ipc_parse_version
While reading through the sysvipc implementation, I noticed that the n32 semctl/shmctl/msgctl system calls behave differently based on whether o32 support is enabled or not: Without o32, the IPC_64 flag passed by user space is rejected but calls without that flag get IPC_64 behavior. As far as I can tell, this was inadvertently changed by a cleanup patch but never noticed by anyone, possibly nobody has tried using sysvipc on n32 after linux-3.19. Change it back to the old behavior now. Fixes: 78aaf956ba3a ("MIPS: Compat: Fix build error if CONFIG_MIPS32_COMPAT but no compat ABI.") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Paul Burton <paul.burton@mips.com> Cc: linux-mips@vger.kernel.org Cc: stable@vger.kernel.org # 3.19+
Diffstat (limited to '')
-rw-r--r--arch/mips/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 787290781b8c..0d14f51d0002 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -3155,6 +3155,7 @@ config MIPS32_O32
config MIPS32_N32
bool "Kernel support for n32 binaries"
depends on 64BIT
+ select ARCH_WANT_COMPAT_IPC_PARSE_VERSION
select COMPAT
select MIPS32_COMPAT
select SYSVIPC_COMPAT if SYSVIPC