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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <429982ba-e06f-e76b-061c-39db67558aa5@intel.com>
Date:   Mon, 31 Oct 2022 14:37:43 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Alexey Dobriyan <adobriyan@...il.com>,
        "H. Peter Anvin" <hpa@...or.com>
Cc:     tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
        dave.hansen@...ux.intel.com, linux-kernel@...r.kernel.org,
        x86@...nel.org
Subject: Re: [PATCH v2] selftests/x86: add "ffff8" -- kernel memory scanner

On 10/29/22 10:25, Alexey Dobriyan wrote:
> 
> 	$ ./ffff8_64 -h
> 	usage: ./ffff8_64 [-f] [-r] [-n N] [-s S]
> 	        -f: sequential scan
> 	        -r: random scan (default)
> 	        -n: use N threads (default: $(nproc))
> 	        -s: lowest address shift (default: 47)
> 	        -t: time to run (default: 256 seconds)

Does this mean that if someone is just running all kernel selftests,
they need to wait for 256 seconds for this to finish?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ