linux-kernel - Re: [PATCH v2 6/6] selftests/mm: remove local __NR

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]

Message-ID: <4dc1c0b8-c38a-455c-8dd2-dab25f912498@intel.com>
Date: Thu, 13 Feb 2025 07:00:55 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: John Hubbard <jhubbard@...dia.com>,
 Andrew Morton <akpm@...ux-foundation.org>, Jeff Xu <jeffxu@...omium.org>,
 Shuah Khan <shuah@...nel.org>
Cc: Andrei Vagin <avagin@...gle.com>,
 Axel Rasmussen <axelrasmussen@...gle.com>,
 Christian Brauner <brauner@...nel.org>, David Hildenbrand
 <david@...hat.com>, Kees Cook <kees@...nel.org>,
 Kent Overstreet <kent.overstreet@...ux.dev>,
 "Liam R . Howlett" <Liam.Howlett@...cle.com>,
 Muhammad Usama Anjum <usama.anjum@...labora.com>,
 Peter Xu <peterx@...hat.com>, Rich Felker <dalias@...c.org>,
 linux-mm@...ck.org, linux-kselftest@...r.kernel.org,
 LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 6/6] selftests/mm: remove local __NR_* definitions

On 2/13/25 00:04, John Hubbard wrote:
> 
> 2) I'm unable to reproduce what you saw, because in ALL cases (before
> or after the commit, and with or without a revert), I get the same
> results on my Intel test machine:
> 
>     $ ./protection_keys_64
>     has pkeys: 0
>     running PKEY tests for unsupported CPU/OS
> 
> ...so that's why I'm attaching a patch, in case you can verify that a
> revert fixes it.

The revert fixes it for me, thanks!

You probably just have hardware without pkey support. This isn't 100%
definitive, but you can check:

	cat /proc/cpuinfo  | grep ospke

If that doesn't match the "flags" line, then your hardware doesn't have
support in the first place and the message is totally expected.