From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] userfaultfd03.c: Require kernel 6.1
Date: Tue, 31 Mar 2026 00:53:53 +0200 [thread overview]
Message-ID: <20260330225353.GA108555@pevik> (raw)
In-Reply-To: <acqPsJkCQXlH9gx5@yuki.lan>
> Hi!
> > > > > > > Nothing besides trying to fix 6.11 (which was not the case) and trying to
> > > > > > > simplify. But whole effort is somehow relevant to general checking test
> > > > > > > requirements cleanup (we had a discussion runtime checks vs. kconfig/min_kver
> > > > > > > which resulted in Cyril's "lib: tst_kconfig: Add runtime checks" [2]).
> > > > > > I guess that the check for all userfaultfd tests should be moved to the
> > > > > > tst_kconfig.c once my patch that adds runtime checks there is in.
> > > > > Or I can send a V3 that adds that check as well.
> > > > Sure, having /dev/userfaultfd in kconfig check would be a benefit. Thanks!
> > > However it looks like we cannot do that, the /dev/userfaultfd was added
> > > into 6.1 while the usefaultfd syscall existed since 4.3. Hence tests
> > > that need /dev/userfaultfd need additional checks.
> > We require for userfaultfd05.c also CONFIG_HAVE_ARCH_USERFAULTFD_WP=y.
> > Maybe bound /dev/userfaultfd check to it? OTOH
> > CONFIG_HAVE_ARCH_USERFAULTFD_WP=y is much older (v5.19-rc1) and original commit
> > in 6.1 [1] does not refer to it.
> Does not work either, the /dev/userfaultfd was added without any changes
> in CONFIG. If we wanted this as generic funcitionality we would have to
> add .needs_devices field into tst_test structure but as far as I my
> grepping shows, usefaultfd is at the moment the only test that depends
> on a device that has been added recently so it does not look like
> it's worth the trouble.
Agree (not worth of the trouble).
Thanks for checking.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-03-30 22:54 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
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 [this message]
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=20260330225353.GA108555@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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.