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: <20220531114021.25a8ab92ad112a4b9f985ebe@linux-foundation.org>
Date:   Tue, 31 May 2022 11:40:21 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Kalpana Shetty <kalpana.shetty@....com>
Cc:     <shuah@...nel.org>, <linux-mm@...ck.org>,
        <linux-kselftest@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] selftests/vm: Add protection_keys tests to run_vmtests

On Tue, 31 May 2022 15:55:56 +0530 Kalpana Shetty <kalpana.shetty@....com> wrote:

> --- a/tools/testing/selftests/vm/run_vmtests.sh
> +++ b/tools/testing/selftests/vm/run_vmtests.sh
> @@ -179,4 +179,11 @@ run_test ./ksm_tests -N -m 1
>  # KSM test with 2 NUMA nodes and merge_across_nodes = 0
>  run_test ./ksm_tests -N -m 0
>  
> +# protection_keys tests
> +if [ $VADDR64 -eq 0 ]; then
> +	run_test ./protection_keys_32
> +else
> +	run_test ./protection_keys_64
> +fi
> +
>  exit $exitcode

So we're presently not running this test at all, unless invoked by
hand?

I'm thinking we should backport this fix - have you any idea when we
broke it?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ