From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andreas Schwab" <schwab@suse.de>, "Florian Weimer" <fweimer@redhat.com>
Cc: linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Catalin Marinas" <catalin.marinas@arm.com>
Subject: Re: syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least
Date: Thu, 01 Aug 2024 14:20:45 +0200 [thread overview]
Message-ID: <838053e0-b186-4e9f-9668-9a3384a71f23@app.fastmail.com> (raw)
In-Reply-To: <mvmh6c4fors.fsf@suse.de>
On Thu, Aug 1, 2024, at 13:47, Andreas Schwab wrote:
> On Aug 01 2024, Florian Weimer wrote:
>
>> It's been repported that __NR_newfstatat has gone missing from the UAPI
>> headers.
>
> It has actually been wrongly renamed to __NR_fstatat.
Ah, I see what happened now, this was part of a semi-automated
conversion from the old format and I incorrectly split up the
entries between 32-bit and 64-bit.
There is another bug in the same entry, since in the meantime,
we have also decided to make newfstat/newfstatat unconditional
again for all 64-bit architectures, and this hasn't made it into
the new syscall.tbl format. This one is only important for
loongarch64.
I'll fix up both ASAP, thanks a lot for the report!
Arnd
prev parent reply other threads:[~2024-08-01 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 11:28 syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least Florian Weimer
2024-08-01 11:47 ` Andreas Schwab
2024-08-01 12:20 ` 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=838053e0-b186-4e9f-9668-9a3384a71f23@app.fastmail.com \
--to=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=fweimer@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=schwab@suse.de \
/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