linux-kernel - Re: [GIT PULL] nolibc for 6.11-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5cccbde4-b296-4759-9ae4-bf1b65f24c5b@linuxfoundation.org>
Date: Mon, 15 Jul 2024 09:50:12 -0600
From: Shuah Khan <skhan@...uxfoundation.org>
To: Thomas Weißschuh <linux@...ssschuh.net>,
 "Paul E. McKenney" <paulmck@...nel.org>
Cc: Willy Tarreau <w@....eu>, linux-kernel@...r.kernel.org,
 Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [GIT PULL] nolibc for 6.11-rc1

On 7/15/24 01:00, Thomas Weißschuh wrote:
> On 2024-07-14 09:44:55+0000, Paul E. McKenney wrote:
>> On Sun, Jul 14, 2024 at 10:09:13AM +0200, Thomas Weißschuh wrote:
>>> On 2024-07-12 20:16:13+0000, Paul E. McKenney wrote:
>>>> On Sun, Jun 30, 2024 at 09:06:39AM -0700, Paul E. McKenney wrote:
>>>>> On Sat, Jun 29, 2024 at 01:04:08PM +0200, Thomas Weißschuh wrote:
>>>>>> Hi Paul,
>>>>>>
>>>>>> The following changes since commit f2661062f16b2de5d7b6a5c42a9a5c96326b8454:
>>>>>>
>>>>>>    Linux 6.10-rc5 (2024-06-23 17:08:54 -0400)
>>>>>>
>>>>>> are available in the Git repository at:
>>>>>>
>>>>>>    https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git tags/nolibc-20240629-for-6.11-1
>>>>>>
>>>>>> for you to fetch changes up to 6ca8f2e20bd1ced8a7cd12b3ae4b1ceca85cfc2b:
>>>>>>
>>>>>>    selftests: kselftest: also use strerror() on nolibc (2024-06-29 09:44:58 +0200)
>>>>>
>>>>> Hearing no objections, I have pulled this in so that it will appear
>>>>> in the next -next.  Here are the test results:
>>>>>
>>>>> make run:
>>>>> 195 test(s): 195 passed,   0 skipped,   0 failed => status: success
>>>>>
>>>>> make run-user:
>>>>> 195 test(s): 193 passed,   2 skipped,   0 failed => status: warning
>>>>>
>>>>> So looks good to me!
>>>
>>> For testing you can use "./run-tests.sh -m [user | system]" to run the
>>> tests on all supported architectures via QEMU.
>>>
>>> (On the first run you can use "-p" to download the toolchains)
>>
>> Thank you for the info!
>>
>> My near-term plan is that I do a smoke test on x86 (or whatever I am
>> running), and let you guys cover the various architectures.  Longer
>> term, I might get more into cross-architecture work.
> 

Thank for fielding this time. Next one in on me.

> I'll try to remember to add the full testreport for future
> pullrequests, too.
> 

Thanks - that will be great.

I run the nolibc tests before I send PR - I also compare to see if my
results match with yours.

thanks,
-- Shuah