diff options
author | Arnd Bergmann <arnd@arndb.de> | 2019-01-10 17:24:31 +0100 |
---|---|---|
committer | Paul Burton <paul.burton@mips.com> | 2019-01-11 11:23:58 -0800 |
commit | 5a9372f751b5350e0ce3d2ee91832f1feae2c2e5 (patch) | |
tree | b405c318cc8d8654857045a255cac16b48964515 /security | |
parent | a214720cbf50cd8c3f76bbb9c3f5c283910e9d33 (diff) | |
download | linux-stable-5a9372f751b5350e0ce3d2ee91832f1feae2c2e5.tar.gz linux-stable-5a9372f751b5350e0ce3d2ee91832f1feae2c2e5.tar.bz2 linux-stable-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 'security')
0 files changed, 0 insertions, 0 deletions