From: Dev Jain <dev.jain@arm.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>
Cc: kernel@collabora.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Anshuman.Khandual@arm.com
Subject: Re: [PATCH v2 12/12] selftests/mm: virtual_address_range: conform to TAP format output
Date: Thu, 14 Mar 2024 10:30:44 +0530 [thread overview]
Message-ID: <12b0aa90-3b4f-4fb0-b4df-c677f496cb09@arm.com> (raw)
In-Reply-To: <20240202113119.2047740-13-usama.anjum@collabora.com>
On 2/2/24 17:01, Muhammad Usama Anjum wrote:
> Conform the layout, informational and status messages to TAP. No
> functional change is intended other than the layout of output messages.
>
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> ---
> .../selftests/mm/virtual_address_range.c | 44 +++++++++----------
> 1 file changed, 22 insertions(+), 22 deletions(-)
>
> diff --git a/tools/testing/selftests/mm/virtual_address_range.c b/tools/testing/selftests/mm/virtual_address_range.c
> index bae0ceaf95b13..7bcf8d48256a6 100644
> --- a/tools/testing/selftests/mm/virtual_address_range.c
> +++ b/tools/testing/selftests/mm/virtual_address_range.c
> @@ -12,6 +12,7 @@
> #include <errno.h>
> #include <sys/mman.h>
> #include <sys/time.h>
> +#include "../kselftest.h"
>
> /*
> * Maximum address range mapped with a single mmap()
> @@ -68,23 +69,15 @@ static char *hind_addr(void)
> return (char *) (1UL << bits);
> }
>
> -static int validate_addr(char *ptr, int high_addr)
> +static void validate_addr(char *ptr, int high_addr)
> {
> unsigned long addr = (unsigned long) ptr;
>
> - if (high_addr) {
> - if (addr < HIGH_ADDR_MARK) {
> - printf("Bad address %lx\n", addr);
> - return 1;
> - }
> - return 0;
> - }
> + if (high_addr && addr < HIGH_ADDR_MARK)
> + ksft_exit_fail_msg("Bad address %lx\n", addr);
>
> - if (addr > HIGH_ADDR_MARK) {
> - printf("Bad address %lx\n", addr);
> - return 1;
> - }
> - return 0;
> + if (addr > HIGH_ADDR_MARK)
> + ksft_exit_fail_msg("Bad address %lx\n", addr);
> }
>
> static int validate_lower_address_hint(void)
> @@ -107,23 +100,29 @@ int main(int argc, char *argv[])
> char *hint;
> unsigned long i, lchunks, hchunks;
>
> + ksft_print_header();
> + ksft_set_plan(1);
> +
> for (i = 0; i < NR_CHUNKS_LOW; i++) {
> ptr[i] = mmap(NULL, MAP_CHUNK_SIZE, PROT_READ | PROT_WRITE,
> MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
>
> if (ptr[i] == MAP_FAILED) {
> - if (validate_lower_address_hint())
> - return 1;
> + if (validate_lower_address_hint()) {
> + ksft_test_result_skip("Memory constraint not fulfilled\n");
> + ksft_finished();
> + }
Hi,
When validate_lower_address_hint() returns 1, it implies that despite
filling the lower
range, mmap succeeded. IMHO, ksft_exit_fail_msg() should be used
instead, with a
more descriptive message indicating that the memory was unexpectedly
allocated.
Regards
Dev
> break;
> }
>
> - if (validate_addr(ptr[i], 0))
> - return 1;
> + validate_addr(ptr[i], 0);
> }
> lchunks = i;
> hptr = (char **) calloc(NR_CHUNKS_HIGH, sizeof(char *));
> - if (hptr == NULL)
> - return 1;
> + if (hptr == NULL) {
> + ksft_test_result_skip("Memory constraint not fulfilled\n");
> + ksft_finished();
> + }
>
> for (i = 0; i < NR_CHUNKS_HIGH; i++) {
> hint = hind_addr();
> @@ -133,8 +132,7 @@ int main(int argc, char *argv[])
> if (hptr[i] == MAP_FAILED)
> break;
>
> - if (validate_addr(hptr[i], 1))
> - return 1;
> + validate_addr(hptr[i], 1);
> }
> hchunks = i;
>
> @@ -145,5 +143,7 @@ int main(int argc, char *argv[])
> munmap(hptr[i], MAP_CHUNK_SIZE);
>
> free(hptr);
> - return 0;
> +
> + ksft_test_result_pass("Test\n");
> + ksft_finished();
> }
next prev parent reply other threads:[~2024-03-14 5:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 11:31 [PATCH v2 00/12] conform tests " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 01/12] selftests/mm: map_fixed_noreplace: conform test " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 02/12] selftests/mm: map_hugetlb: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 03/12] selftests/mm: map_populate: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 04/12] selftests/mm: mlock-random-test: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 05/12] selftests/mm: mlock2-tests: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 06/12] selftests/mm: mrelease_test: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 07/12] selftests/mm: mremap_dontunmap: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 08/12] selftests/mm: split_huge_page_test: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 09/12] selftests/mm: thp_settings: conform " Muhammad Usama Anjum
2024-02-14 17:19 ` Ryan Roberts
2024-02-14 18:00 ` Ryan Roberts
2024-02-15 4:59 ` Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 10/12] selftests/mm: thuge-gen: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 11/12] selftests/mm: transhuge-stress: " Muhammad Usama Anjum
2024-02-02 11:31 ` [PATCH v2 12/12] selftests/mm: virtual_address_range: " Muhammad Usama Anjum
2024-03-14 5:00 ` Dev Jain [this message]
2024-03-14 8:46 ` Muhammad Usama Anjum
2024-03-14 12:22 ` [PATCH] selftests/mm: virtual_address_range: Switch to ksft_exit_fail_msg Dev Jain
2024-03-14 12:33 ` Muhammad Usama Anjum
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=12b0aa90-3b4f-4fb0-b4df-c677f496cb09@arm.com \
--to=dev.jain@arm.com \
--cc=Anshuman.Khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.com \
/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