linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] selftests/mm: Report unique test names for each cow test
Date: Tue, 3 Jun 2025 17:06:17 +0200	[thread overview]
Message-ID: <df85fba8-826f-41fb-8850-077a4e4dd240@redhat.com> (raw)
In-Reply-To: <e3d584fe-6297-403d-84f3-397a0fe459c5@sirena.org.uk>

On 03.06.25 16:58, Mark Brown wrote:
> On Tue, Jun 03, 2025 at 04:15:42PM +0200, David Hildenbrand wrote:
>> On 03.06.25 15:21, Mark Brown wrote:
> 
>>>>>     	} else {
>>>>> -		ksft_test_result_fail("Leak from parent into child\n");
> 
>>>> Same here and in other cases below (I probably didn't catch all).
> 
>>>> We should log that somehow to indicate what exactly is going wrong, likely
>>>> using ksft_print_msg().
> 
>>> Can you send a patch with the logging that you think would be clear
>>> please?
>>> I dropped these because they just seemed to be reporting the> overall
>> point of the test, unlike the cases where we ran into some error
>>> during the setup and didn't actually manage to perform the test we were
>>> trying to do.  Perhaps the tests should be renamed.
> 
>> ksft_print_msg("Leak from parent into child");
> 
> Can you send a patch showing when/where you want this printing please?

I'm really busy right now, unfortunately.

> Like I said I suspect the test name is just unclear here...

I would hope we find some mechanical replacement.

E.g.,

ksft_test_result_pass("No leak from parent into child\n");

becomes

ksft_print_msg("No leak from parent into child\n");
log_test_result(KSFT_PASS);

and

ksft_test_result_xfail("Leak from parent into child\n");

becomes

ksft_print_msg("Leak from parent into child\n");
log_test_result(KSFT_FAIL);

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2025-06-03 15:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 16:04 [PATCH v2 0/4] selftests/mm: cow and gup_longterm cleanups Mark Brown
2025-05-27 16:04 ` [PATCH v2 1/4] selftests/mm: Use standard ksft_finished() in cow and gup_longterm Mark Brown
2025-05-27 16:04 ` [PATCH v2 2/4] selftests/mm: Add helper for logging test start and results Mark Brown
2025-06-03 12:37   ` David Hildenbrand
2025-06-03 18:27     ` Mark Brown
2025-06-03 20:18       ` David Hildenbrand
2025-05-27 16:04 ` [PATCH v2 3/4] selftests/mm: Report unique test names for each cow test Mark Brown
2025-06-03 12:51   ` David Hildenbrand
2025-06-03 13:21     ` Mark Brown
2025-06-03 14:15       ` David Hildenbrand
2025-06-03 14:58         ` Mark Brown
2025-06-03 15:06           ` David Hildenbrand [this message]
2025-06-03 15:22             ` Mark Brown
2025-06-03 16:57               ` David Hildenbrand
2025-06-03 17:48                 ` Mark Brown
2025-06-03 17:55                   ` Mark Brown
2025-06-03 20:21                     ` David Hildenbrand
2025-05-27 16:04 ` [PATCH v2 4/4] selftests/mm: Fix test result reporting in gup_longterm Mark Brown
2025-06-03 12:36   ` David Hildenbrand
2025-06-03 13:05     ` Mark Brown
2025-06-05 16:00   ` Lorenzo Stoakes
2025-06-05 16:15     ` Mark Brown
2025-06-05 16:26       ` Lorenzo Stoakes
2025-06-05 16:42         ` Mark Brown
2025-06-05 16:55           ` David Hildenbrand
2025-06-05 17:19             ` Mark Brown
2025-06-05 17:34               ` David Hildenbrand
2025-06-05 18:24                 ` Mark Brown
2025-06-05 17:09           ` Lorenzo Stoakes
2025-06-05 17:38             ` Mark Brown
2025-06-05 17:47               ` Lorenzo Stoakes
2025-06-05 18:29                 ` Mark Brown
2025-06-05 18:35                   ` Lorenzo Stoakes
2025-06-05 16:48       ` David Hildenbrand
2025-06-05 20:32         ` Andrew Morton

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=df85fba8-826f-41fb-8850-077a4e4dd240@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=shuah@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;
as well as URLs for NNTP newsgroup(s).