From: Jakub Jelinek <jakub@redhat.com>
To: Rudi Heitbaum <rudi@heitbaum.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andreas Schwab <schwab@suse.de>,
Florian Weimer <fweimer@redhat.com>,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, linux-api@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, WANG Xuerui <kernel@xen0n.name>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev
Subject: Re: [PATCH] syscalls: fix syscall macros for newfstat/newfstatat
Date: Sat, 3 Aug 2024 10:00:41 +0200 [thread overview]
Message-ID: <Zq3jqeq6USL066k+@tucnak> (raw)
In-Reply-To: <Zq28wejX3U9J1_JV@faede8dcc269>
On Sat, Aug 03, 2024 at 05:14:41AM +0000, Rudi Heitbaum wrote:
> With this patch to kernel 6.11-rc1 the error whilst compiling gcc-14.2 for
> aarch64 with libsanitizer has changed from '__NR_newfstatat' to
> '__NR_fstat', so some change, but still fail8ng.
>
> sanitizer_syscall_linux_aarch64.inc:13:23: error: '__NR_newfstatat' was not declared in this scope
> 13 | #define SYSCALL(name) __NR_ ## name
> | ^~~~~
>
> sanitizer_syscall_linux_aarch64.inc:13:23: error: '__NR_fstat' was not declared in this scope
> 13 | #define SYSCALL(name) __NR_ ## name
> | ^~~~~
Probably it would be useful to check
echo '#include <asm/unistd.h>' | gcc -E -dD -xc - | grep '#define __NR_' | sort
for all arches between 6.10 and the latest git, diff them and resolve any
unintended differences.
Jakub
next prev parent reply other threads:[~2024-08-03 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 12:32 [PATCH] syscalls: fix syscall macros for newfstat/newfstatat Arnd Bergmann
2024-08-03 5:14 ` Rudi Heitbaum
2024-08-03 8:00 ` Jakub Jelinek [this message]
2024-08-03 8:12 ` Arnd Bergmann
2024-08-05 19:53 ` Jakub Jelinek
2024-08-05 21:07 ` 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=Zq3jqeq6USL066k+@tucnak \
--to=jakub@redhat.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=fweimer@redhat.com \
--cc=kernel@xen0n.name \
--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=loongarch@lists.linux.dev \
--cc=mhiramat@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rudi@heitbaum.com \
--cc=schwab@suse.de \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).