From: Shuah Khan <skhan@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Greg KH <greg@kroah.com>,
stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
stable-commits@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Patch "selftests: vDSO: skip getrandom test if architecture is unsupported" has been added to the 6.11-stable tree
Date: Thu, 3 Oct 2024 10:53:18 -0600 [thread overview]
Message-ID: <fa9e15b3-4478-4ba7-a00a-6632c98271a3@linuxfoundation.org> (raw)
In-Reply-To: <Zv20olVBlnxL9UnS@zx2c4.com>
On 10/2/24 15:01, Jason A. Donenfeld wrote:
> On Wed, Oct 02, 2024 at 01:45:57PM -0600, Shuah Khan wrote:
>> This is not different from other kernel APIs and enhancements and
>> correspo0nding updates to the existing selftests.
>>
>> The
>> vdso_test_getrandom test a user-space program exists in 6.11.
>>
>> Use should be able to run vdso_test_getrandom compiled on 6.12
>> repo on a 6.11 kernel.
>> vdso_test_getrandom test a user-space program exists in 6.11.
>> Users should be able to run vdso_test_getrandom compiled on 6.12
>> repo on a 6.11 kernel. This is what several CIs do.
>
> The x86 test from 6.12 works just fine on 6.11.
Yes x86 test is a good example to look at that handles 32-bit
and 640-bit issues you brought up in your email.
That is reason why I asked you to refer to x86 Makefile to
solve the architecture differences related to this test you
mentioned in your email.
>
> I really don't follow you at all or what you're getting at. I think if
> you actually look at the code, you'll be mostly okay with it. And if
> there's something that looks awry to you, send a patch or describe to me
> clearly what looks wrong and I'll send a patch.
To be very clear about the selftest guidelines (covered in
kselftest.rst document)
1. Ideally selftests should compile on all architectures.
Exception to this are few architecture specific
features which can be selectively compiled either
with ifdef statements in the code or Makefile arch
checks.
The goal is to keep these to a minimum so we can a wide
range of tests in CIs and other test systems.
2. Selftest from mainline should run on stable releases
handling missing features and missing config options
with skip so we don't have to deal false failures.
The goal is to minimize false negatives and false positives.
3. Reported results are clear to the users and testers.
Thank you for the patches. I will review your patches and give you
feedback.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-10-03 16:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240930231443.2560728-1-sashal@kernel.org>
2024-10-01 3:56 ` Patch "selftests: vDSO: skip getrandom test if architecture is unsupported" has been added to the 6.11-stable tree Jason A. Donenfeld
2024-10-01 14:43 ` Shuah Khan
2024-10-01 14:45 ` Jason A. Donenfeld
2024-10-01 14:56 ` Shuah Khan
2024-10-01 15:03 ` Jason A. Donenfeld
2024-10-01 15:29 ` Shuah Khan
2024-10-02 4:13 ` Jason A. Donenfeld
2024-10-02 6:21 ` Greg KH
2024-10-02 17:00 ` Jason A. Donenfeld
2024-10-02 19:45 ` Shuah Khan
2024-10-02 21:01 ` Jason A. Donenfeld
2024-10-03 16:53 ` Shuah Khan [this message]
2024-10-03 16:58 ` Jason A. Donenfeld
2024-10-03 17:22 ` Jason A. Donenfeld
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=fa9e15b3-4478-4ba7-a00a-6632c98271a3@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=greg@kroah.com \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.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