Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp661203pxy; Wed, 5 May 2021 10:35:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw4TASFE8vK79S0CT5qtbQmUynzQhXeDOVypKV1t4yl2LRXjxOmABLQmUHBXoEnPCTteAc+ X-Received: by 2002:a17:902:7c91:b029:ed:5748:901e with SMTP id y17-20020a1709027c91b02900ed5748901emr32481789pll.27.1620236138958; Wed, 05 May 2021 10:35:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620236138; cv=none; d=google.com; s=arc-20160816; b=CMbh+ZVExN0Lqod3lPrAzoo2F8NAuPipYubAdMUayX4dddCzgcKoJInRqLjdLyHN1e JMTS80fGJOdrytUILsGqY0JvBzNenZrpcRsP96mjfOb06jTaH9V1JQ3rPKfdd1m7nEmo ZgXBOvzsjYRTbtPzaFlttochA7y1wnQbtOWxv2TR6+Z1B2OTCp/X9BvqG8d8GmfoaJMr GUQtrlfV0cNCVu5G0IOTM0rcpeCCaHUUzXMHM0xTsoATnF5+fjq1ZqOfYqyPeRD6EO30 DHtaHvzMlVPEBRkIqsfI6dCgtjWC/WhETZ6wvthd7jXDmcjqdDjSHgvv+XvVX0NEi/7L bAeQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=aqiKpvrbIKEUFcPaEHpWlX7/EqGVA+x2KDHDrAUhtew=; b=kForgheM8VrAtSKwfICc3HMiCx3WDVpdEQjsjBgi4hleO+ph+bl/+4Vh6VSVre8E41 H4xz4f9s9hAVt/UEV6WqolVGvcqSi8cOzY0egYaIxB1nAslA6C9iuN6MUU8x10Hk3hbg aFqdlsgGaJ1k3hpYw/3WbKQn11BqRFLIn0o75RpPHjeHhsLg9MYKyHDWVWo2ViozlFB5 IF9NrxakGGrKGuPm4g+rcOS2k6GmdPy9uDwbXQd9Ib0h+vpU7UhFn9VWgYjD+YvkvQAS gwGAeMD4S0ag94l23p7zmdVfky5pQRyclf1VAFgEW7Xdk4491F/PS/aT6DKzBNhRhVYW lspA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 136si5554594pfz.261.2021.05.05.10.35.26; Wed, 05 May 2021 10:35:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235458AbhEERdY (ORCPT + 99 others); Wed, 5 May 2021 13:33:24 -0400 Received: from foss.arm.com ([217.140.110.172]:49074 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238688AbhEERbR (ORCPT ); Wed, 5 May 2021 13:31:17 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id E25811FB; Wed, 5 May 2021 10:30:19 -0700 (PDT) Received: from C02TD0UTHF1T.local (unknown [10.57.28.242]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id BF0D03F70D; Wed, 5 May 2021 10:30:17 -0700 (PDT) Date: Wed, 5 May 2021 18:30:14 +0100 From: Mark Rutland To: He Zhe Cc: oleg@redhat.com, catalin.marinas@arm.com, will@kernel.org, linux-arm-kernel@lists.infradead.org, paul@paul-moore.com, eparis@redhat.com, linux-audit@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/3] arm64: syscall.h: Add sign extension handling in syscall_get_return_value for compat Message-ID: <20210505173014.GE5605@C02TD0UTHF1T.local> References: <20210423103533.30121-1-zhe.he@windriver.com> <20210423103533.30121-2-zhe.he@windriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210423103533.30121-2-zhe.he@windriver.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Fri, Apr 23, 2021 at 06:35:32PM +0800, He Zhe wrote: > Add sign extension handling in syscall_get_return_value so that it can > handle 32-bit compatible case and can be used by for example audit, just > like what syscall_get_error does. > > Suggested-by: Mark Rutland > Signed-off-by: He Zhe > --- > v1 to v2: Improve error code check suggested by Mark > > arch/arm64/include/asm/syscall.h | 15 ++++++++++++++- > 1 file changed, 14 insertions(+), 1 deletion(-) > > diff --git a/arch/arm64/include/asm/syscall.h b/arch/arm64/include/asm/syscall.h > index cfc0672013f6..c3b5fca82ff4 100644 > --- a/arch/arm64/include/asm/syscall.h > +++ b/arch/arm64/include/asm/syscall.h > @@ -44,7 +44,20 @@ static inline long syscall_get_error(struct task_struct *task, > static inline long syscall_get_return_value(struct task_struct *task, > struct pt_regs *regs) > { > - return regs->regs[0]; > + long val = regs->regs[0]; > + long error = val; > + > + if (compat_user_mode(regs)) > + error = sign_extend64(error, 31); > + > + /* > + * Return codes with bit 31 set may or may not be an error code. > + * For example, mmap may return a legal 32 bit address with bit 31 set > + * for 32 bit thread, in which case the untouched val should be > + * returned. Otherwise, the sign-extended error should be returned if > + * it still falls in error number range. > + */ > + return IS_ERR_VALUE(error) ? error : val; I'm afraid I have misled you here. I wrote up a test that uses PTRACE_GET_SYSCALL_INFO, and I found that on a 32-bit arm (v5.12) kernel, *all* syscall return values get sign-extended after all. For example, if (on a 32-bit kernel) I use MAP_FIXED to mmap() at address 0x8bad0000, the return value reported in ptrace_syscall_info::exit::rval is 0xffffffff8bad0000. So for that we shoudn't have the IS_ERR_VALUE() check after all, but I'm not currently sure whether there are other cases where 32-bit arm wouldn't sign-extend, and I think we'll need to dig into this some more. Thanks, Mark.