From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/2] selftests/nolibc: small simplification of test development phase
Date: Mon, 23 Jan 2023 20:12:50 +0100 [thread overview]
Message-ID: <20230123191250.GD13172@1wt.eu> (raw)
In-Reply-To: <20230123174003.GU2948950@paulmck-ThinkPad-P17-Gen-1>
On Mon, Jan 23, 2023 at 09:40:03AM -0800, Paul E. McKenney wrote:
> Except that when I install Ubuntu 20.04's version, I get this:
>
> ------------------------------------------------------------------------
>
> $ sudo make run-user
> MKDIR sysroot/x86/include
> make[1]: Entering directory '/home/git/linux-rcu/tools/include/nolibc'
> make[2]: Entering directory '/home/git/linux-rcu'
> make[2]: Leaving directory '/home/git/linux-rcu'
> make[2]: Entering directory '/home/git/linux-rcu'
> INSTALL /home/git/linux-rcu/tools/testing/selftests/nolibc/sysroot/sysroot/include
> make[2]: Leaving directory '/home/git/linux-rcu'
> make[1]: Leaving directory '/home/git/linux-rcu/tools/include/nolibc'
> CC nolibc-test
> 32 gettimeofday_null = -1 EFAULT [FAIL]
> See all results in /home/git/linux-rcu/tools/testing/selftests/nolibc/run.out
>
> ------------------------------------------------------------------------
>
> I have attached run.out.
>
> In contrast, with my hand-built qemu-x86_64, all tests passed.
>
> This might be just a version-related bug, but figured I should let you
> guys know.
Interesting. Maybe something differs in the way it passes expectedly
invalid pointers to some syscalls. Keep in mind that it's using your
local kernel also, that could make a difference. I'm not that much keen
on trying to investigate that one to be honest, given that this user
mode is really meant to ease the life of test developers like Ammar
and myself who just want to focus on the correctness of the test they're
adding and not that much on the validity of the test itself in this
context. I suggest we keep this one in mind without putting too much
effort on it for now.
Thanks!
Willy
next prev parent reply other threads:[~2023-01-23 19:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 8:53 [PATCH 0/2] selftests/nolibc: small simplification of test development phase Willy Tarreau
2023-01-21 8:53 ` [PATCH 1/2] selftests/nolibc: support "x86_64" for arch name Willy Tarreau
2023-01-21 8:53 ` [PATCH 2/2] selftests/nolibc: add a "run-user" target to test the program in user land Willy Tarreau
2023-01-21 20:00 ` [PATCH 0/2] selftests/nolibc: small simplification of test development phase Paul E. McKenney
2023-01-21 21:34 ` Willy Tarreau
2023-01-23 16:47 ` Paul E. McKenney
2023-01-23 17:17 ` Willy Tarreau
2023-01-23 17:34 ` Paul E. McKenney
2023-01-23 16:57 ` Ammar Faizi
2023-01-23 17:09 ` Paul E. McKenney
2023-01-23 17:20 ` Willy Tarreau
2023-01-23 17:31 ` Ammar Faizi
2023-01-23 17:37 ` Willy Tarreau
2023-01-23 17:40 ` Ammar Faizi
2023-01-23 17:40 ` Paul E. McKenney
2023-01-23 19:01 ` Ammar Faizi
2023-01-23 19:12 ` Paul E. McKenney
2023-01-23 19:12 ` Willy Tarreau [this message]
2023-01-23 19:25 ` Paul E. McKenney
2023-01-23 17:34 ` Ammar Faizi
2023-01-23 17:52 ` Paul E. McKenney
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=20230123191250.GD13172@1wt.eu \
--to=w@1wt.eu \
--cc=ammarfaizi2@gnuweeb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=shuah@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