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
Date: Wed, 10 Jan 2024 14:42:22 +0100 [thread overview]
Message-ID: <6c82c4b9-297d-44a0-87dc-9413e15fa48a@app.fastmail.com> (raw)
In-Reply-To: <20240110130122.3836513-1-nik.borisov@suse.com>
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
prev parent reply other threads:[~2024-01-10 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 13:01 [PATCH RESEND] x86/entry/ia32: Ensure s32 is sign extended to s64 Nikolay Borisov
2024-01-10 13:42 ` Arnd Bergmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c82c4b9-297d-44a0-87dc-9413e15fa48a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=rpalethorpe@suse.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox