All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Joey Gouly <joey.gouly@arm.com>, linux-arm-kernel@lists.infradead.org
Cc: nd@arm.com, broonie@kernel.org, catalin.marinas@arm.com,
	shuah@kernel.org, will@kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 3/6] kselftest/arm64: mte: user_mem: check different offsets and sizes
Date: Fri, 4 Feb 2022 08:57:07 -0700	[thread overview]
Message-ID: <cdcdb0d5-990e-1fc8-0c3e-ac8c87d3d3bd@linuxfoundation.org> (raw)
In-Reply-To: <20220203143620.30629-4-joey.gouly@arm.com>

On 2/3/22 7:36 AM, Joey Gouly wrote:
> Iterate over different file offsets, pointer offsets and buffer sizes to exercise
> and test different behaviour.

Please add more information here.

> 
> Signed-off-by: Joey Gouly <joey.gouly@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Shuah Khan <shuah@kernel.org>
> ---
>   .../selftests/arm64/mte/check_user_mem.c      | 49 +++++++++++--------
>   1 file changed, 29 insertions(+), 20 deletions(-)
> 
> diff --git a/tools/testing/selftests/arm64/mte/check_user_mem.c b/tools/testing/selftests/arm64/mte/check_user_mem.c
> index e5bfeaeb64bb..35061ae23ed5 100644
> --- a/tools/testing/selftests/arm64/mte/check_user_mem.c
> +++ b/tools/testing/selftests/arm64/mte/check_user_mem.c
> @@ -26,6 +26,8 @@ static int check_usermem_access_fault(int mem_type, int mode, int mapping,
>   	char val = 'A';
>   	size_t len, read_len;
>   	void *ptr, *ptr_next;
> +	int fileoff, ptroff, size;
> +	int sizes[] = {1, 2, 3, 8, 16, 32, 4096, page_sz};
>   
>   	err = KSFT_PASS;
>   	len = 2 * page_sz;
> @@ -66,26 +68,33 @@ static int check_usermem_access_fault(int mem_type, int mode, int mapping,
>   	ptr_next = mte_insert_new_tag(ptr_next);
>   	mte_set_tag_address_range(ptr_next, tag_len);
>   
> -	lseek(fd, 0, 0);
> -	/* Copy from file into buffer with invalid tag */
> -	read_len = read(fd, ptr, len);
> -	mte_wait_after_trig();
> -	/*
> -	 * Accessing user memory in kernel with invalid tag should fail in sync
> -	 * mode without fault but may not fail in async mode as per the
> -	 * implemented MTE userspace support in Arm64 kernel.
> -	 */
> -	if (cur_mte_cxt.fault_valid) {
> -		err = KSFT_FAIL;


> -		goto usermem_acc_err;
> -	}
> -	if (mode == MTE_SYNC_ERR && read_len < len) {
> -		/* test passed */
> -	} else if (mode == MTE_ASYNC_ERR && read_len == len) {
> -		/* test passed */
> -	} else {
> -		err = KSFT_FAIL;

Why not set err in usermem_acc_err - this way you can make the error
paths common and simpler.

> -		goto usermem_acc_err;
> +	for (fileoff = 0; fileoff < 16; fileoff++) {
> +		for (ptroff = 0; ptroff < 16; ptroff++) {
> +			for (i = 0; i < ARRAY_SIZE(sizes); i++) {
> +				size = sizes[i];
> +				lseek(fd, 0, 0);
> +				/* Copy from file into buffer with invalid tag */
> +				read_len = read(fd, ptr + ptroff, size);
> +				mte_wait_after_trig();
> +				/*
> +				 * Accessing user memory in kernel with invalid tag should fail in sync
> +				 * mode without fault but may not fail in async mode as per the
> +				 * implemented MTE userspace support in Arm64 kernel.
> +				 */
> +				if (cur_mte_cxt.fault_valid) {
> +					err = KSFT_FAIL;

The above assignment can go way if you add this to usermem_acc_err
path

> +					goto usermem_acc_err;
> +				}
> +				if (mode == MTE_SYNC_ERR && read_len < len) {
> +					/* test passed */
> +				} else if (mode == MTE_ASYNC_ERR && read_len == size) {
> +					/* test passed */
> +				} else {
> +					err = KSFT_FAIL;

Same here

> +					goto usermem_acc_err;
> +				}
> +			}
> +		}
>   	}
>   usermem_acc_err:
>   	mte_free_memory((void *)ptr, len, mem_type, true);
> 

With the above requested changes -

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

thanks,
-- Shuah

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-02-04 15:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 14:36 [PATCH v2 0/6] add more tests to MTE kselftests Joey Gouly
2022-02-03 14:36 ` [PATCH v2 1/6] kselftest/arm64: mte: user_mem: introduce tag_offset and tag_len Joey Gouly
2022-02-04 15:51   ` Shuah Khan
2022-02-03 14:36 ` [PATCH v2 2/6] kselftest/arm64: mte: user_mem: rework error handling Joey Gouly
2022-02-04 15:54   ` Shuah Khan
2022-02-03 14:36 ` [PATCH v2 3/6] kselftest/arm64: mte: user_mem: check different offsets and sizes Joey Gouly
2022-02-04 15:57   ` Shuah Khan [this message]
2022-02-03 14:36 ` [PATCH v2 4/6] kselftest/arm64: mte: user_mem: add test type enum Joey Gouly
2022-02-04 15:59   ` Shuah Khan
2022-02-03 14:36 ` [PATCH v2 5/6] kselftest/arm64: mte: user_mem: add more test types Joey Gouly
2022-02-04 16:01   ` Shuah Khan
2022-02-03 14:36 ` [PATCH v2 6/6] kselftest/arm64: mte: user_mem: test more combinations of values Joey Gouly
2022-02-04 16:02   ` Shuah Khan
2022-02-04 14:18 ` [PATCH v2 0/6] add more tests to MTE kselftests Mark Brown
2022-02-04 16:06 ` Shuah Khan

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=cdcdb0d5-990e-1fc8-0c3e-ac8c87d3d3bd@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=nd@arm.com \
    --cc=shuah@kernel.org \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.