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] [day] [month] [year] [list]
Date:   Wed, 15 Dec 2021 09:59:11 +0000
From:   Cristian Marussi <cristian.marussi@....com>
To:     kernel test robot <oliver.sang@...el.com>
Cc:     0day robot <lkp@...el.com>, LKML <linux-kernel@...r.kernel.org>,
        lkp@...ts.01.org, linux-kselftest@...r.kernel.org,
        sjpark@...zon.de, keescook@...omium.org, shuah@...nel.org
Subject: Re: [selftests/kselftest/runner.sh]  3226b4a464:
 kernel-selftests.cpu-hotplug.cpu-on-off-test.sh.fail

On Mon, Dec 13, 2021 at 01:20:44PM +0800, kernel test robot wrote:
> 
> 
> Greeting,
> 
> FYI, we noticed the following commit (built with gcc-9):
> 

Hi,

> commit: 3226b4a4648c6562c642947cee8b90335df911f5 ("[PATCH] selftests/kselftest/runner.sh: Add optional command parameters in settings")
> url: https://github.com/0day-ci/linux/commits/Cristian-Marussi/selftests-kselftest-runner-sh-Add-optional-command-parameters-in-settings/20211202-222205
> base: https://git.kernel.org/cgit/linux/kernel/git/shuah/linux-kselftest.git next
> patch link: https://lore.kernel.org/linux-kselftest/20211202142056.17386-1-cristian.marussi@arm.com
> 
> in testcase: kernel-selftests
> version: kernel-selftests-x86_64-99d09ee9-1_20211206
> with following parameters:
> 
> 	group: group-01
> 	ucode: 0xde
> 
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
> 
> 

This commit was under discussion/not acked nor fully reviewed, not ready
for upstream queuing really.

Indeed I posted today a V2 that take a different approach:

https://lore.kernel.org/linux-kselftest/20211215095340.50717-1-cristian.marussi@arm.com/T/#u

and should solve also the issue mentioned in this report.

Thanks,
Cristian

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ