Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
	shuah@kernel.org, hpa@zytor.com, x86@kernel.org,
	dave.hansen@linux.intel.com, bp@alien8.de, mingo@redhat.com,
	tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	kirill@shutemov.name, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4 0/3] selftests/lam: get_user additions and LAM enabled check
Date: Tue, 26 Nov 2024 09:34:36 -0700	[thread overview]
Message-ID: <2cff1613-9fd0-4c9e-ad02-970ac8614cec@linuxfoundation.org> (raw)
In-Reply-To: <cover.1732627541.git.maciej.wieczor-retman@intel.com>

On 11/26/24 06:34, Maciej Wieczor-Retman wrote:
> Recent change in how get_user() handles pointers [1] has a specific case
> for LAM. It assigns a different bitmask that's later used to check
> whether a pointer comes from userland in get_user().
> 
> While currently commented out (until LASS [2] is merged into the kernel)
> it's worth making changes to the LAM selftest ahead of time.
> 
> Modify cpu_has_la57() so it provides current paging level information
> instead of the cpuid one.
> 
> Add test case to LAM that utilizes a ioctl (FIOASYNC) syscall which uses
> get_user() in its implementation. Execute the syscall with differently
> tagged pointers to verify that valid user pointers are passing through
> and invalid kernel/non-canonical pointers are not.
> 
> Also to avoid unhelpful test failures add a check in main() to skip
> running tests if LAM was not compiled into the kernel.
> 
> Code was tested on a Sierra Forest Xeon machine that's LAM capable. The
> test was ran without issues with both the LAM lines from [1] untouched
> and commented out. The test was also ran without issues with LAM_SUP
> both enabled and disabled.
> 
> 4/5 level pagetables code paths were also successfully tested in Simics
> on a 5-level capable machine.
> 
> [1] https://lore.kernel.org/all/20241024013214.129639-1-torvalds@linux-foundation.org/
> [2] https://lore.kernel.org/all/20241028160917.1380714-1-alexander.shishkin@linux.intel.com/
> 
> Maciej Wieczor-Retman (3):
>    selftests/lam: Move cpu_has_la57() to use cpuinfo flag
>    selftests/lam: Skip test if LAM is disabled
>    selftests/lam: Test get_user() LAM pointer handling
> 
>   tools/testing/selftests/x86/lam.c | 122 ++++++++++++++++++++++++++++--
>   1 file changed, 117 insertions(+), 5 deletions(-)
> 

Looks good to me. For selftests if it is going through x86 tree.

Acked-by: Shuah Khan <skhan@linuxfoundation.org>

If you want me to take this through selftest tree, I can do that.

thanks,
-- Shuah

  parent reply	other threads:[~2024-11-26 16:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 13:34 [PATCH v4 0/3] selftests/lam: get_user additions and LAM enabled check Maciej Wieczor-Retman
2024-11-26 13:34 ` [PATCH v4 1/3] selftests/lam: Move cpu_has_la57() to use cpuinfo flag Maciej Wieczor-Retman
2024-11-27 12:11   ` Kirill A. Shutemov
2024-11-27 13:15     ` Maciej Wieczor-Retman
2024-11-26 13:34 ` [PATCH v4 2/3] selftests/lam: Skip test if LAM is disabled Maciej Wieczor-Retman
2024-11-26 13:34 ` [PATCH v4 3/3] selftests/lam: Test get_user() LAM pointer handling Maciej Wieczor-Retman
2024-11-26 16:34 ` Shuah Khan [this message]
2024-11-27 17:47   ` [PATCH v4 0/3] selftests/lam: get_user additions and LAM enabled check Maciej Wieczor-Retman
2024-11-27 12:13 ` Kirill A. Shutemov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2cff1613-9fd0-4c9e-ad02-970ac8614cec@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=mingo@redhat.com \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox