Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp638790pxy; Thu, 22 Apr 2021 09:57:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJynb2P+8wE5WjTT6mHv0kaj59BcfDS5s6skN9OopCQ8ETnJ/XXOIbajZer5zx51LMSQIQ9X X-Received: by 2002:a05:6402:34c4:: with SMTP id w4mr5205247edc.367.1619110636100; Thu, 22 Apr 2021 09:57:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619110636; cv=none; d=google.com; s=arc-20160816; b=TJDKJJCLCpzcWDsc4camBz02SXt0qYK1PKOxyu+HYNkEjzNuVXP9shyrIZsxLpC5fY HX7UVmbJ0bmxlRODTOt3XXj1QnDBByyIij2e+bqE68XTYhvL2UNdO7NhmVsLyH73yd67 JqO/evATUBr0iLUgQdA41Cn+MsOdLimgtOmH+Np4gJlz9RtJd6jPd0t6e83ce2JiHRKW L5bMoKD8qT/E82VyMGQzcUaBNIJJcIc6udQbHkh+kZN0ei2h5Sxa+ksIS3spkTQeCcO6 NJxzpXlQJyhn39CYtofDH6oZm3K5cFVRDzuahOmQU/azrJJHINy8oUpWNjcqlSS75Y7z e81g== 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=2/xhyW4ngMkvNKiQYmSP3vtDbn0yh9J8uNr9azyb+wo=; b=KP28atTYs3V2ev8i9lwNPoA64RXvHouiIvlfB4QL85aL0/Wzv908q+6Mh5dLRPYb5k YuMA4oNhxgj3t9+uYzcf/sLNzl5gJObJ7D+Pf6/gazgzRtx1T0SIizw9T+KVfiF5E29y PndFaxiCsHZUJVoSEZeUA9KcsVU51mtonveYvyG6bBD40geXAtR0o9i7Qm5R9JPT2P6Y 3YrRh0O02YlFYfHNpeth8h5o04wpYuY9iT8s/RFSJZR4R3TqrF8lPs8LGrk9dSmF9UMt GRzr6Ko4A5iXTsbh9Sh/htjr7L0LO1i91cIk1aqV/xUAKxFuMkBVOfQDrTFY3fgI7l9t MS2w== 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 v16si2803917ejg.513.2021.04.22.09.56.53; Thu, 22 Apr 2021 09:57:16 -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 S238182AbhDVQ4Z (ORCPT + 99 others); Thu, 22 Apr 2021 12:56:25 -0400 Received: from foss.arm.com ([217.140.110.172]:53868 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238156AbhDVQ4Y (ORCPT ); Thu, 22 Apr 2021 12:56:24 -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 076B311D4; Thu, 22 Apr 2021 09:55:49 -0700 (PDT) Received: from C02TD0UTHF1T.local (unknown [10.57.22.241]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 73A843F694; Thu, 22 Apr 2021 09:55:47 -0700 (PDT) Date: Thu, 22 Apr 2021 17:55:45 +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 2/3] arm64: syscall.h: Add sign extension handling in syscall_get_return_value for compat Message-ID: <20210422165545.GE66392@C02TD0UTHF1T.local> References: <20210416075533.7720-1-zhe.he@windriver.com> <20210416075533.7720-2-zhe.he@windriver.com> <20210421174105.GB52940@C02TD0UTHF1T.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210421174105.GB52940@C02TD0UTHF1T.local> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 21, 2021 at 06:41:05PM +0100, Mark Rutland wrote: > On Fri, Apr 16, 2021 at 03:55: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. > > If a compat syscall can ever legitimately return a non-error value with > bit 31 set, and this sign-extends it, is that ever going to reach > userspace as a 64-bit value? > > IIUC things like mmap() can return pointers above 2GiB for a compat > task, so I'm a bit uneasy that we'd handle those wrong. I can't see a > way of preventing that unless we keep the upper 32 bits for errors. Looking at this with fresh eyes, I think we can more closely mirror syscall_get_error(), and do something like: static inline long syscall_get_return_value(struct task_struct *task, struct pt_regs *regs) { long val = regs->regs[0]; long error = val; if (is_compat_thread(task_thread_info(task))) error = sign_extend64(error, 31); return IS_ERR_VALUE(error) ? error : val; } Thanks, Mark. > > Mark. > > > > > Signed-off-by: He Zhe > > --- > > arch/arm64/include/asm/syscall.h | 7 ++++++- > > 1 file changed, 6 insertions(+), 1 deletion(-) > > > > diff --git a/arch/arm64/include/asm/syscall.h b/arch/arm64/include/asm/syscall.h > > index cfc0672013f6..cd7a22787aeb 100644 > > --- a/arch/arm64/include/asm/syscall.h > > +++ b/arch/arm64/include/asm/syscall.h > > @@ -44,7 +44,12 @@ 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]; > > + > > + if (is_compat_thread(task_thread_info(task))) > > + val = sign_extend64(val, 31); > > + > > + return val; > > } > > > > static inline void syscall_set_return_value(struct task_struct *task, > > -- > > 2.17.1 > >