From: Zi Yan <ziy@nvidia.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Pedro Falcato <pfalcato@suse.de>,
Adam Sindelar <adam@wowsignal.io>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] selftests/mm: skip uffd tests in madv_guard if uffd is not present.
Date: Thu, 15 May 2025 14:46:41 -0400 [thread overview]
Message-ID: <6601AD88-C2B7-47DA-B75C-46AFEE1BD2AC@nvidia.com> (raw)
In-Reply-To: <ec648245-c771-4e4a-b355-a86c99ad8143@lucifer.local>
On 15 May 2025, at 14:41, Lorenzo Stoakes wrote:
> Ah you got to this first :) thanks!
>
> Could you do this with a cover letter though? It's really weird to have 2/2
> reply to 1/2, I know sometimes people do that, but it's just odd, and it'd be
> good to have an overview, thanks!
>
> On Thu, May 15, 2025 at 02:23:32PM -0400, Zi Yan wrote:
>> When userfaultfd is not compiled into kernel, userfaultfd() returns -1,
>> causing uffd tests in madv_guard fail. Skip the tests instead.
>
> 'madv_guard'? I'd just say the guard_regions.uffd test to fail.
Sure. Will change it.
>
>>
>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>> ---
>> tools/testing/selftests/mm/guard-regions.c | 17 +++++++++++++++--
>> 1 file changed, 15 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/testing/selftests/mm/guard-regions.c b/tools/testing/selftests/mm/guard-regions.c
>> index 0cd9d236649d..93af3d3760f9 100644
>> --- a/tools/testing/selftests/mm/guard-regions.c
>> +++ b/tools/testing/selftests/mm/guard-regions.c
>> @@ -1453,8 +1453,21 @@ TEST_F(guard_regions, uffd)
>>
>> /* Set up uffd. */
>> uffd = userfaultfd(0);
>> - if (uffd == -1 && errno == EPERM)
>> - ksft_exit_skip("No userfaultfd permissions, try running as root.\n");
>
> Let's just make this all part of the same switch please!
What do you mean? EPERM is handled in the switch-case below.
>
> And while I originally used ksft_exit_skip(), I think we can just use the
> SKIP(return, ...) form here just fine to keep it consistent.
Right. I am using SKIP below, since when I ran it, ksft_exit_skip()
makes the whole test message inconsistent.
>
>> + if (uffd == -1) {
>> + switch (errno) {
>> + case EPERM:
>> + SKIP(return, "No userfaultfd permissions, try running as root.");
>> + break;
>> + case ENOSYS:
>> + SKIP(return, "userfaultfd is not supported/not enabled.");
>> + break;
>> + default:
>> + ksft_exit_fail_msg("userfaultfd failed with %s\n",
>> + strerror(errno));
>> + break;
>> + }
>> + }
>> +
>> ASSERT_NE(uffd, -1);
>>
>> ASSERT_EQ(ioctl(uffd, UFFDIO_API, &api), 0);
>> --
>> 2.47.2
>>
>
> Thanks!
--
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2025-05-15 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 18:23 Zi Yan
2025-05-15 18:23 ` [PATCH 2/2] selftests/mm: skip hugevm test if kernel config file " Zi Yan
2025-05-15 18:43 ` Lorenzo Stoakes
2025-05-15 19:15 ` Pedro Falcato
2025-05-15 18:41 ` [PATCH 1/2] selftests/mm: skip uffd tests in madv_guard if uffd " Lorenzo Stoakes
2025-05-15 18:46 ` Zi Yan [this message]
2025-05-15 18:49 ` Lorenzo Stoakes
2025-05-15 18:53 ` Zi Yan
2025-05-15 19:11 ` Pedro Falcato
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=6601AD88-C2B7-47DA-B75C-46AFEE1BD2AC@nvidia.com \
--to=ziy@nvidia.com \
--cc=adam@wowsignal.io \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
/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