From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, valentin.schneider@arm.com,
mark.rutland@arm.com
Subject: Re: rcutorture initrd/nolibc build on ARMv8?
Date: Tue, 19 Jan 2021 17:19:01 +0100 [thread overview]
Message-ID: <20210119161901.GA14667@1wt.eu> (raw)
In-Reply-To: <20210119153147.GA5083@paulmck-ThinkPad-P72>
Hi Paul,
On Tue, Jan 19, 2021 at 07:31:47AM -0800, Paul E. McKenney wrote:
> Hello, Willy,
>
> Some people are having trouble running rcutorture on ARMv8. They
> get things like this from the nolibc build of initrd:
>
> https://paste.debian.net/1181762/
>
> The nolibc.h file says this:
>
> /* Some archs (at least aarch64) don't expose the regular syscalls anymore by
> * default, either because they have an "_at" replacement, or because there are
> * more modern alternatives. For now we'd rather still use them.
> */
>
> Are these build failures expected behavior on ARMv8?
No, I don't think so. I'm regularly building my own init using this,
and it works on various platforms including aarch64, while it makes
use of a number of such syscalls.
From what I'm seeing, this seems to happen each time in such a construct:
#if defined(__NR_new_name)
use __NR_new_name
#else
use __NR_old_name
#endif
with the error appearing on old_name. So I guess that we're rather facing a
case where a number of such __NR_* entries are not defined because presumably
one include file might be missing (probably from a recent change of headers
dependency).
I can't spot from the report above the original C file that was attempted
to be built, it makes me think we tried to compile directly the .h file.
Having it run through sh -x would help me try to locate the root cause or
possibly even attempt to reproduce it.
Thanks,
Willy
next prev parent reply other threads:[~2021-01-19 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 15:31 rcutorture initrd/nolibc build on ARMv8? Paul E. McKenney
2021-01-19 16:19 ` Willy Tarreau [this message]
2021-01-19 17:02 ` Mark Rutland
2021-01-19 17:16 ` Willy Tarreau
2021-01-19 17:43 ` Willy Tarreau
2021-01-20 12:07 ` Mark Rutland
2021-01-20 12:43 ` Willy Tarreau
2021-01-20 13:45 ` Mark Rutland
2021-01-20 14:25 ` Willy Tarreau
2021-01-20 14:37 ` Mark Rutland
2021-01-20 14:54 ` Mark Rutland
2021-01-20 15:02 ` Willy Tarreau
2021-01-21 3:50 ` Willy Tarreau
2021-02-12 12:37 ` [tip: core/rcu] tools/nolibc: Remove incorrect definitions of __ARCH_WANT_* tip-bot2 for Willy Tarreau
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=20210119161901.GA14667@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=paulmck@kernel.org \
--cc=valentin.schneider@arm.com \
/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).