From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Shuah Khan <skhan@linuxfoundation.org>
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>
Subject: Re: Patch "selftests: vDSO: skip getrandom test if architecture is unsupported" has been added to the 6.11-stable tree
Date: Wed, 2 Oct 2024 23:01:22 +0200 [thread overview]
Message-ID: <Zv20olVBlnxL9UnS@zx2c4.com> (raw)
In-Reply-To: <7657fb39-da01-4db9-b4b2-5801c38733e4@linuxfoundation.org>
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.
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.
next prev parent reply other threads:[~2024-10-02 21:01 UTC|newest]
Thread overview: 31+ 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 [this message]
2024-10-03 3:13 ` [PATCH kselftest 0/3] getrandom & chacha cleanups Jason A. Donenfeld
2024-10-03 3:13 ` [PATCH kselftest 1/3] selftests: vDSO: condition chacha build on chacha implementation Jason A. Donenfeld
2024-10-03 3:13 ` [PATCH kselftest 2/3] selftests: vDSO: unconditionally build getrandom test Jason A. Donenfeld
2024-10-03 3:13 ` [PATCH kselftest 3/3] selftests: vDSO: improve getrandom and chacha error messages Jason A. Donenfeld
2024-10-06 3:35 ` kernel test robot
2024-10-06 4:35 ` Jason A. Donenfeld
2024-10-06 4:40 ` [PATCH kselftest v2 1/4] selftests: vDSO: condition chacha build on chacha implementation Jason A. Donenfeld
2024-10-06 4:40 ` [PATCH kselftest v2 2/4] selftests: vDSO: unconditionally build getrandom test Jason A. Donenfeld
2024-10-06 4:40 ` [PATCH kselftest v2 3/4] selftests: vDSO: improve getrandom and chacha error messages Jason A. Donenfeld
2024-10-06 4:40 ` [PATCH kselftest v2 4/4] selftests: vDSO: unconditionally build chacha test Jason A. Donenfeld
2024-10-07 20:53 ` Shuah Khan
2024-10-07 21:45 ` [PATCH kselftest v3 1/3] " Jason A. Donenfeld
2024-10-07 21:45 ` [PATCH kselftest v3 2/3] selftests: vDSO: unconditionally build getrandom test Jason A. Donenfeld
2024-10-07 21:45 ` [PATCH kselftest v3 3/3] selftests: vDSO: improve getrandom and chacha error messages Jason A. Donenfeld
2024-10-08 21:36 ` [PATCH kselftest v3 1/3] selftests: vDSO: unconditionally build chacha test Shuah Khan
2024-10-03 17:18 ` [PATCH kselftest 4/3] " Jason A. Donenfeld
2024-10-03 22:42 ` [PATCH kselftest 0/3] getrandom & chacha cleanups Shuah Khan
2024-10-03 16:53 ` Patch "selftests: vDSO: skip getrandom test if architecture is unsupported" has been added to the 6.11-stable tree Shuah Khan
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=Zv20olVBlnxL9UnS@zx2c4.com \
--to=jason@zx2c4.com \
--cc=greg@kroah.com \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.