From: Cyril Hrubis <chrubis@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] epoll_pwait06: Skip BPF map file descriptor
Date: Wed, 24 Sep 2025 10:56:12 +0200 [thread overview]
Message-ID: <aNOyLCG_Yhv4Rk30@yuki.lan> (raw)
In-Reply-To: <20250923154827.74305-1-mdoucha@suse.cz>
Hi!
> Older kernels don't support waiting for BPF map file descriptors using
> epoll. Skip the subtest, other file descriptor types are sufficient.
>
> Signed-off-by: Martin Doucha <mdoucha@suse.cz>
> ---
>
> epoll_ctl(EPOLL_CTL_ADD) returns EPERM for BPF map file descriptor
> on kernel v4.12.
>
> testcases/kernel/syscalls/epoll_pwait/epoll_pwait06.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/testcases/kernel/syscalls/epoll_pwait/epoll_pwait06.c b/testcases/kernel/syscalls/epoll_pwait/epoll_pwait06.c
> index 3bedc2cf5..d47327bed 100644
> --- a/testcases/kernel/syscalls/epoll_pwait/epoll_pwait06.c
> +++ b/testcases/kernel/syscalls/epoll_pwait/epoll_pwait06.c
> @@ -36,6 +36,7 @@ static void run(void)
> case TST_FD_DIR:
> case TST_FD_DEV_ZERO:
> case TST_FD_PROC_MAPS:
> + case TST_FD_BPF_MAP:
> case TST_FD_FSOPEN:
> case TST_FD_FSPICK:
> case TST_FD_OPEN_TREE:
Can we make this kernel version dependent? I do not like disabling tests
that work on newer kernels just because it does not work on something
that is eight years old.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-09-24 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 15:48 [LTP] [PATCH] epoll_pwait06: Skip BPF map file descriptor Martin Doucha
2025-09-24 8:56 ` Cyril Hrubis [this message]
2025-09-24 11:06 ` Martin Doucha
2025-09-24 11:52 ` Cyril Hrubis
2025-09-24 11:59 ` Martin Doucha
2025-09-24 12:08 ` Cyril Hrubis
2025-09-24 13:06 ` Martin Doucha
2025-09-24 13:16 ` Cyril Hrubis
2025-09-26 14:07 ` 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=aNOyLCG_Yhv4Rk30@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox