linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>,
	David Hildenbrand <david@redhat.com>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/4] selftests/mm: Fix test result reporting in gup_longterm
Date: Thu, 5 Jun 2025 17:15:51 +0100	[thread overview]
Message-ID: <722628a8-f3fd-4fb9-ae04-2313a52ffb36@sirena.org.uk> (raw)
In-Reply-To: <a76fc252-0fe3-4d4b-a9a1-4a2895c2680d@lucifer.local>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

On Thu, Jun 05, 2025 at 05:00:49PM +0100, Lorenzo Stoakes wrote:

> This seems to be causing tests to fail rather than be skipped if hugetlb
> isn't configured. I bisected the problem to this patch so it's definitely
> changed how things are handled (though of course it might just be
> _revealing_ some previously existing bug in this test...).

> Using a couple of tests as an example:

> Before this patch:

> # [RUN] R/O longterm GUP-fast pin in MAP_PRIVATE file mapping ... with memfd hugetlb (2048 kB)
> # memfd_create() failed (Cannot allocate memory)
> not ok 39 R/O longterm GUP-fast pin in MAP_PRIVATE file mapping ... with memfd hugetlb (2048 kB)
> # [RUN] R/O longterm GUP-fast pin in MAP_PRIVATE file mapping ... with memfd hugetlb (1048576 kB)
> # memfd_create() failed (Cannot allocate memory)
> not ok 40 R/O longterm GUP-fast pin in MAP_PRIVATE file mapping ... with memfd hugetlb (1048576 kB)

That's the thing with memfd being special and skipping on setup failure
that David mentioned, I've got a patch as part of the formatting series
I was going to send after the merge window.  

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-06-05 16:15 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
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 [this message]
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=722628a8-f3fd-4fb9-ae04-2313a52ffb36@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=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