From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8FDAC2F3A0 for ; Mon, 21 Jan 2019 14:09:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A980720861 for ; Mon, 21 Jan 2019 14:09:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548079774; bh=wR5w45Yb4/fud0h/RZD6NHFIn1QttTT1pZaqaUfQPDs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=2fB3YmKhloEXGKQA6F+DrP4++/wrZPfxlc28/Xt3iTId+CZAE1qwDnP/QcewRPlP8 YT0AVy6/8Q5zSSKXcpQcWa3skoaH1yca3cR/9RWzXxanYntIMi+M99uy5IgsAYkimD 5Iv7EeG3gTkTShyO8VXkxJro5jd03csB170ggtWA= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731709AbfAUOJc (ORCPT ); Mon, 21 Jan 2019 09:09:32 -0500 Received: from mail.kernel.org ([198.145.29.99]:39758 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730551AbfAUNzN (ORCPT ); Mon, 21 Jan 2019 08:55:13 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6F5E520861; Mon, 21 Jan 2019 13:55:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548078912; bh=wR5w45Yb4/fud0h/RZD6NHFIn1QttTT1pZaqaUfQPDs=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=DWOKMncHA38jq0HiaNOMCyL9cx4M7tvvwY2mCeLhJuTisQiBnqALz6dn6cUvyN5h3 9dtsvas5twS3xoEKLZcFHkPz5gbnLkbhJwPQigCZW1XC1RTOJepL6hqCSgVdw6nnXs PqwXRaZ+eb5GufkAn7rulDm1iccgy3+aWPqna360= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Arnd Bergmann , Paul Burton , linux-mips@vger.kernel.org Subject: [PATCH 4.9 27/51] mips: fix n32 compat_ipc_parse_version Date: Mon, 21 Jan 2019 14:44:23 +0100 Message-Id: <20190121122456.105302155@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190121122453.700446926@linuxfoundation.org> References: <20190121122453.700446926@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.9-stable review patch. If anyone has any objections, please let me know. ------------------ From: Arnd Bergmann commit 5a9372f751b5350e0ce3d2ee91832f1feae2c2e5 upstream. 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 Signed-off-by: Paul Burton Cc: linux-mips@vger.kernel.org Cc: stable@vger.kernel.org # 3.19+ Signed-off-by: Greg Kroah-Hartman --- arch/mips/Kconfig | 1 + 1 file changed, 1 insertion(+) --- a/arch/mips/Kconfig +++ b/arch/mips/Kconfig @@ -3135,6 +3135,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