From: Mark Brown <broonie@kernel.org>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: Fix test result reporting in gup_longterm
Date: Fri, 16 May 2025 19:07:46 +0100 [thread overview]
Message-ID: <aCd-8kEyDm2f2w0z@finisterre.sirena.org.uk> (raw)
In-Reply-To: <46d151d7-c04b-4538-9725-dc4f46ac8ac1@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]
On Fri, May 16, 2025 at 04:12:08PM +0200, David Hildenbrand wrote:
> On 16.05.25 15:09, Mark Brown wrote:
> > > I'm afraid we have other such tests that report duplicate conditions. cow.c
> > > is likely another candidate (written by me ;) ).
> > That one's not come up for me (this was one of four different patches
> > for mm selftests I sent the other day cleaning up duplicate test names).
> $ sudo ./cow
...
> 1..778
> # [INFO] Anonymous memory tests in private mappings
> # [RUN] Basic COW after fork() ... with base page
> ok 1 No leak from parent into child
> # [RUN] Basic COW after fork() ... with swapped out base page
> ok 2 No leak from parent into child
> Aren't the duplicate "No leak from parent into child" the problematic bits?
> But maybe I am getting it wrong, what needs to be "unique" :)
Ah, yes - that's got the same issue. I'm not running that program one
way or another, it's not immediately clear to me why not - I can't see
any sign of it being invoked by the runner script but I also can't see
anything that I'd expect to stop that happening. I'll have to have a
poke at it, thanks for flagging that.
[Converting to kselftet_harness]
> > That'd certainly work, though doing that is more surgery on the test
> > than I personally have the time/enthusiasm for right now.
> Same over here.
> But probably if we touch it, we should just clean it up right away. Well,
> if we decide that that is the right cleanup. (you mention something like that
> in your patch description :)
OTOH there's something to be said for just making incremental
improvements in the tests where we can, they tend not to get huge
amounts of love in general which means perfect can very much be the
enemy of good. If there's some immediate prospect of someone doing a
bigger refactoring then that'd be amazing, but if not then it seems
useful to make things play better with the automation for now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-16 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 8:57 Mark Brown
2025-05-15 9:35 ` Dev Jain
2025-05-15 9:41 ` Mark Brown
2025-05-15 9:43 ` Dev Jain
2025-05-16 8:02 ` David Hildenbrand
2025-05-16 12:29 ` Mark Brown
2025-05-16 12:55 ` David Hildenbrand
2025-05-16 13:09 ` Mark Brown
2025-05-16 14:12 ` David Hildenbrand
2025-05-16 18:07 ` Mark Brown [this message]
2025-05-19 13:28 ` David Hildenbrand
2025-05-19 14:55 ` Mark Brown
2025-05-21 18:48 ` Mark Brown
2025-05-22 8:42 ` David Hildenbrand
2025-05-22 9:23 ` Mark Brown
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=aCd-8kEyDm2f2w0z@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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