Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 31 May 2022 11:40:21 -0700
From:   Andrew Morton <akpm@linux-foundation.org>
To:     Kalpana Shetty <kalpana.shetty@amd.com>
Cc:     <shuah@kernel.org>, <linux-mm@kvack.org>,
        <linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests/vm: Add protection_keys tests to run_vmtests
Message-Id: <20220531114021.25a8ab92ad112a4b9f985ebe@linux-foundation.org>
In-Reply-To: <20220531102556.388-1-kalpana.shetty@amd.com>
References: <20220531102556.388-1-kalpana.shetty@amd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 31 May 2022 15:55:56 +0530 Kalpana Shetty <kalpana.shetty@amd.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?