From: Li Wang via ltp <ltp@lists.linux.it>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] userfaultfd03.c: Require kernel 6.1
Date: Fri, 27 Mar 2026 13:41:07 +0800 [thread overview]
Message-ID: <acYYc47HXGYa5Mqj@redhat.com> (raw)
In-Reply-To: <20260326125216.159239-1-pvorel@suse.cz>
On Thu, Mar 26, 2026 at 01:52:15PM +0100, Petr Vorel wrote:
> Required kernel functionality was added in kernel 6.1 (not 6.11)
> 2d5de004e009 ("userfaultfd: add /dev/userfaultfd for fine grained access control")
>
> Because it's a new kernel functionality which has not been backported to
> enterprise kernels we can simplify check with just .min_kver.
>
> Fixes: b63ab54aee ("userfaultfd: Do not use min_kver as gate for test")
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> Hi all,
>
> @Li I suppose RHEL kernel haven't backport this.
Why do you lack confidence in RHEL? haha :)
I have confimed that both RHEL 9 and 10 have backported this
feature (commit 2d5de004e009).
As RHEL 9 is based on an older kernel(5.14) but includes this
backport, changing this to .min_kver = "6.1" will cause the
test to be incorrectly skipped (TCONF) on RHEL 9 systems.
Anyway, back to the topic, what is the point of creating this patch?
Anything I missed?
--
Regards,
Li Wang
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-27 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 12:52 [LTP] [PATCH] userfaultfd03.c: Require kernel 6.1 Petr Vorel
2026-03-26 21:35 ` Ricardo Branco
2026-03-27 5:41 ` Li Wang via ltp [this message]
2026-03-27 9:05 ` Petr Vorel
2026-03-27 13:17 ` Cyril Hrubis
2026-03-27 13:19 ` Cyril Hrubis
2026-03-27 15:17 ` Petr Vorel
2026-03-27 16:07 ` Cyril Hrubis
2026-03-27 16:44 ` Petr Vorel
2026-03-30 14:58 ` Cyril Hrubis
2026-03-30 22:53 ` Petr Vorel
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=acYYc47HXGYa5Mqj@redhat.com \
--to=ltp@lists.linux.it \
--cc=liwang@redhat.com \
--cc=pvorel@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.