public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: linux-riscv@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-api@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>, Catalin Marinas <catalin.marinas@arm.com>
Subject: syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least
Date: Thu, 01 Aug 2024 13:28:04 +0200	[thread overview]
Message-ID: <87sevoqy7v.fsf@oldenburg.str.redhat.com> (raw)

It's been repported that __NR_newfstatat has gone missing from the UAPI
headers.

  [sanitizer] __NR_newfstatat not defined in linux kernel headers in
  aarch64
  <https://github.com/llvm/llvm-project/issues/100098>

  __NR_newfstatat no longer defined on aarch64
  <https://bugzilla.redhat.com/show_bug.cgi?id=2301919>

I suspect that's related to the syscall.tbl refactoring around these
commits:

commit e632bca07c8eef1de9dc50f4e4066c56e9d68b07
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Thu Jul 4 14:33:34 2024 +0200

    arm64: generate 64-bit syscall.tbl

commit 3db80c999debbadd5d627fb30f8b06fee331ffb6
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Wed Apr 24 09:14:39 2024 +0200

    riscv: convert to generic syscall table

Thanks,
Florian



             reply	other threads:[~2024-08-01 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 11:28 Florian Weimer [this message]
2024-08-01 11:47 ` syscall.tbl refactoring seems to have dropped definition of __NR_newfstatat on arm64 and riscv (64-bit) at least Andreas Schwab
2024-08-01 12:20   ` Arnd Bergmann

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=87sevoqy7v.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.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 \
    /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