commit b7cf2c2bced126bdfb7571064fc1d0a56f8a2905 tree ae669613eb28ee5d54e134e9561697ac82ad8401 parent 1840ee23d172b5ab04cca7c2acfa48755b041911 author Petr Vorel 2026-01-22 18:53:54 +0100 committer Li Wang 2026-01-27 20:55:57 +0800 lapi/tls.h: Cleanup ifdefs fe24196ce3 added .supported_archs into clone10. Therefore there is no need to keep architecture check also in lapi/tls.h. Moreover "Unsupported architecture for TLS" was misleading as it looked as a missing arch support in kernel, but it's our allocate_tls_area() implementation which does support only 3 architectures. Signed-off-by: Petr Vorel Reviewed-by: Li Wang Reviewed-by: Andrea Cervesato :100644 100644 f7e2f483fe9e623e669d3f0e9f09d9218b42f216 468fe3086dc2e9445090955b9158f203fc0e0ebe M include/lapi/tls.h commit 1840ee23d172b5ab04cca7c2acfa48755b041911 tree a553735bdedd0405e6fcf01797f946c5d703ca58 parent d69695a846c5e05bbec2d116ec7adfd6871e9970 author Li Wang 2026-01-23 19:54:19 +0800 committer Li Wang 2026-01-27 20:54:53 +0800 userfaultfd05: require CONFIG_HAVE_ARCH_USERFAULTFD_WP Kernels built without arch UFFD-WP support (CONFIG_HAVE_ARCH_USERFAULTFD_WP) can report "WP unsupported" in different ways (e.g. UFFDIO_API returns -1/EINVAL on some newer kernels, while others succeed but do not advertise UFFD_FEATURE_PAGEFAULT_FLAG_WP in the returned features mask). Rather than relying on runtime probing that varies across kernels, require CONFIG_HAVE_ARCH_USERFAULTFD_WP=y via .needs_kconfigs and use SAFE_IOCTL() for UFFDIO_API again. Follow-up: 485a4cd2ba3 ("userfaultfd05: allow TCONF when UFFD-WP is unsupported") Signed-off-by: Li Wang Cc: Ricardo Branco Reviewed-by: Cyril Hrubis :100644 100644 6cae45f201a2fc00dd4a3821ba57e429cb7e628e e25a227cf3e5fdba44bb3fbeadef1f28a7082d68 M testcases/kernel/syscalls/userfaultfd/userfaultfd05.c