From: Thomas Gleixner <tglx@linutronix.de>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Christian Brauner <brauner@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v3] LoongArch: Add support to clone a time namespace
Date: Wed, 31 May 2023 11:21:33 +0200 [thread overview]
Message-ID: <87bki0hn4y.ffs@tglx> (raw)
In-Reply-To: <1685519761-20425-1-git-send-email-yangtiezhu@loongson.cn>
On Wed, May 31 2023 at 15:56, Tiezhu Yang wrote:
> When execute the following command to test clone3 on LoongArch:
>
> # cd tools/testing/selftests/clone3 && make && ./clone3
>
> we can see the following error info:
>
> # [5719] Trying clone3() with flags 0x80 (size 0)
> # Invalid argument - Failed to create new process
> # [5719] clone3() with flags says: -22 expected 0
> not ok 18 [5719] Result (-22) is different than expected (0)
>
> This is because if CONFIG_TIME_NS is not set, but the flag
> CLONE_NEWTIME (0x80) is used to clone a time namespace, it
> will return -EINVAL in copy_time_ns().
Which means that test case is broken.
> With this patch, the following failed test can be fixed too:
You cannot fix a broken test case by enabling functionality which
is not guaranteed to be available on all platforms.
Adding time name spaces on loongarch is a completely separate issue and
has absolutely nothing to do with broken test cases.
They are still broken when CONFIG_TIME_NS is disabled in Kconfig, no?
So this wants to be two separate things:
1) Fix the broken test cases so they handle CONFIG_TIME_NS=n
situations correctly
2) Add support for TIME_NS to loongarch
Thanks,
tglx
next prev parent reply other threads:[~2023-05-31 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 7:56 [PATCH v3] LoongArch: Add support to clone a time namespace Tiezhu Yang
2023-05-31 8:34 ` Youling Tang
2023-05-31 10:02 ` Tiezhu Yang
2023-05-31 9:21 ` Thomas Gleixner [this message]
2023-05-31 10:04 ` Tiezhu Yang
2023-06-03 2:07 ` Youling Tang
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=87bki0hn4y.ffs@tglx \
--to=tglx@linutronix.de \
--cc=brauner@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=luto@kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=yangtiezhu@loongson.cn \
/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