public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Ricardo Branco <rbranco@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] userfaultfd05: handle kernels rejecting WP feature in UFFDIO_API
Date: Fri, 23 Jan 2026 10:45:38 +0100	[thread overview]
Message-ID: <20260123094538.GA113458@pevik> (raw)
In-Reply-To: <20260123054056.131992-1-liwang@redhat.com>

Hi Li, Ricardo,

> Commit 485a4cd2ba3 ("userfaultfd05: allow TCONF when UFFD-WP is unsupported")
> added a TCONF path for missing UFFD-WP, but it relied on checking
> uffdio_api.features after a failed ioctl (on RHEL-10).

> That is not sufficient: it did not handle the case where UFFDIO_API
> succeeds but the kernel does not advertise UFFD_FEATURE_PAGEFAULT_FLAG_WP
> in the returned features mask.

> So userfaultfd05 still fails on RHEL-9 s390x platform:

>     userfaultfd05.c:106: TBROK: ioctl(3,((((2U|1U) << (((0+8)+8)+14)) |
> 		    (((0xAA)) << (0+8)) | ((((0x00))) << 0) |
> 		    ((((sizeof(struct uffdio_register)))) << ((0+8)+8)))),...)
> 		    failed: EINVAL (22)

> Now, let's handle both behaviours by retrying UFFDIO_API with features=0
> on EINVAL and treating a successful retry as "WP unsupported" (TCONF).
> Also check the returned features mask after a successful UFFDIO_API and
> skip when WP is not advertised.

...
>  	if (ioctl(uffd, UFFDIO_API, &uffdio_api) < 0) {
> -		if (!(uffdio_api.features & UFFD_FEATURE_PAGEFAULT_FLAG_WP))
> -			tst_brk(TCONF, "UFFD write-protect unsupported");
> +		int err = errno;
> +		if (err == EINVAL) {
> +			uffdio_api.api = UFFD_API;
> +			uffdio_api.features = 0;
> +
> +			if (ioctl(uffd, UFFDIO_API, &uffdio_api) == 0)
> +				tst_brk(TCONF, "UFFD write-protect unsupported");
> +		}

Wouldn't be better in this case to check kconfig for
CONFIG_HAVE_ARCH_USERFAULTFD_WP (untested, but it should work

Back to our discussion about how often using kconfig [1]. While I prefer to
avoid using it for tristate (kernel might be configured but module missing), but
here is just a feature.

[1] https://lore.kernel.org/ltp/CAASaF6wOSvi+07Pq5O6+f1Hkrq6WWMgpCaooJxWrO9uOvRM3pw@mail.gmail.com/

But I'm ok with it if you prefer exact check.
Reviewed-by: Petr Vorel <pvorel@suse.cz>

> -		tst_brk(TBROK | TERRNO, "ioctl() on userfaultfd failed");
> +		errno = err;
> +		tst_brk(TBROK | TERRNO, "ioctl(UFFDIO_API) failed");
+1
>  	}

Kind regards,
Petr

> +	if (!(uffdio_api.features & UFFD_FEATURE_PAGEFAULT_FLAG_WP))
> +		tst_brk(TCONF, "UFFD write-protect unsupported");
> +
>  	uffdio_register.range.start = (unsigned long) page;
>  	uffdio_register.range.len = page_size;
>  	uffdio_register.mode = UFFDIO_REGISTER_MODE_WP;

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-01-23  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23  5:40 [LTP] [PATCH] userfaultfd05: handle kernels rejecting WP feature in UFFDIO_API Li Wang via ltp
2026-01-23  9:45 ` Petr Vorel [this message]
2026-01-23 11:34   ` Li Wang via ltp
2026-01-23 11:53     ` Petr Vorel
2026-01-23 12:02       ` Li Wang via ltp
2026-01-23 12:25         ` Petr Vorel
2026-01-26  6:02           ` Li Wang via ltp
2026-01-27 12:48 ` Cyril Hrubis

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=20260123094538.GA113458@pevik \
    --to=pvorel@suse.cz \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=rbranco@suse.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