Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp50440pxy; Wed, 21 Apr 2021 18:10:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzV086cw0Jb5oSEisL+mw5sEJqDsVcTgybiBB7M/gGIkt8g9FFDM8WgGkr0GtRaPuN0vDge X-Received: by 2002:a63:2c81:: with SMTP id s123mr902701pgs.168.1619053853319; Wed, 21 Apr 2021 18:10:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619053853; cv=none; d=google.com; s=arc-20160816; b=ATRzGVwmw6uyavyul30rxKbEYxBKGLB6hunNi6li+ELhhY65kxVMPHIp8sSsd2lykN I3hUa+rX4WK2tAPXCjXU2ZBrUUKYuKXlJsjOkCeLAab6qNohG6/CD7rDCIxHVK5o5Rwq d4TzeqL31haDcPalZIgwzPJ0UwmSogYJhlWkSyxhyW2WBKFpXgfKqjIBVkwMqvRPW0wS v03smKzbr81m638HfXqc32INgpBjjAYYVRglKoSS4SauK0gk59iEM2UH+dK6Xwt5H7Jp bz6n8m7hkZOmDffmwA+Ep/G5VgZywyJh9xq1KMW4Kt9WtW2wx+z/YDp33cteSnYa3oVn kYyg== 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=vcAeU2wpPOao18ZQw7/EHhBQrQgIbca79hBD+xyC5yg=; b=h2lnJ8dTOUTnss6STvcRbbt5omkvTQ7c5l6PdayoCTmXTBXXFk9TmC2x2vyuFoUj9G ZVw3CL4a2ZQWGzlmm6W1jvz/GzvyUeiPcYm5CrKNoZkQ6R7xFS7+ueXD5EJCRSoUzvTt /HxI2KPj9FIMQoa5xU9yRwR8TdD39AdrXIMC5Kq+ZlYeV3cS9XrsYk6jaEaahErKaBrM AEYoErKl4XryDJv6sQ+HWY4vw/wxxJ7KWOyd6Darma1b6epFAaTjVgCLnrPKNz1AB0oB Nd3AmZ9499FamBOEGFzTX3ZsbEUP48VEXwXnD6OgkyFdU8E+5FFQXlYe961BidKwZDhA WyNA== 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 z12si1324398pln.80.2021.04.21.18.10.31; Wed, 21 Apr 2021 18:10:53 -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 S244829AbhDURlq (ORCPT + 99 others); Wed, 21 Apr 2021 13:41:46 -0400 Received: from foss.arm.com ([217.140.110.172]:38818 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243098AbhDURlp (ORCPT ); Wed, 21 Apr 2021 13:41:45 -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 A92E311FB; Wed, 21 Apr 2021 10:41:11 -0700 (PDT) Received: from C02TD0UTHF1T.local (unknown [10.57.3.41]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B1FBB3F694; Wed, 21 Apr 2021 10:41:08 -0700 (PDT) Date: Wed, 21 Apr 2021 18:41:05 +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: <20210421174105.GB52940@C02TD0UTHF1T.local> References: <20210416075533.7720-1-zhe.he@windriver.com> <20210416075533.7720-2-zhe.he@windriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210416075533.7720-2-zhe.he@windriver.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. 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 >