Received-SPF: pass (google.com: domain of linux-kernel+bounces-22260-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-1364-ga51d5fd3b7-fm-20231219.001-ga51d5fd3
Precedence: bulk
MIME-Version: 1.0
Message-Id: <6c82c4b9-297d-44a0-87dc-9413e15fa48a@app.fastmail.com>
In-Reply-To: <20240110130122.3836513-1-nik.borisov@suse.com>
References: <20240110130122.3836513-1-nik.borisov@suse.com>
Date: Wed, 10 Jan 2024 14:42:22 +0100
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nikolay Borisov" <nik.borisov@suse.com>, linux-kernel@vger.kernel.org,
 x86@kernel.org
Cc: linux-api@vger.kernel.org, "Richard Palethorpe" <rpalethorpe@suse.com>
Subject: Re: [PATCH RESEND] x86/entry/ia32: Ensure s32 is sign extended to s64
Content-Type: text/plain

On Wed, Jan 10, 2024, at 14:01, Nikolay Borisov wrote:
>
> This patch has been sent previously by Richard back in 2021 [0]. 
> However it
> seems to have been dropped at some point and never merged. So I'm 
> resending again
> to consider it for merging given that io_pgetevents_time64 LTP test 
> still fails.
>
>
> [0] https://lore.kernel.org/all/20210927161955.28494-1-rpalethorpe@suse.com/

Thank you for resending this, I hadn't noticed that this never
went in, but I also see that I still keep the same patch in
my testing tree.

I think the entire syscall entry logic needs a larger
cross-architecture overhaul to avoid these confusing macros
and make sure we get it right everywhere, but that's not
going to happen overnight, so this patch is what should
get merged and backported to LTS kernels first.

    arnd