public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] fanotify25: fix test failure on kernel with CONFIG_MODULES=n
Date: Mon, 2 Mar 2026 16:39:36 +0100	[thread overview]
Message-ID: <aaWvOIlfyIDH7J8A@yuki.lan> (raw)
In-Reply-To: <20260302144446.1291724-1-amir73il@gmail.com>

Hi!
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
>  testcases/kernel/syscalls/fanotify/fanotify25.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/testcases/kernel/syscalls/fanotify/fanotify25.c b/testcases/kernel/syscalls/fanotify/fanotify25.c
> index c982f3225..9b03fd9ab 100644
> --- a/testcases/kernel/syscalls/fanotify/fanotify25.c
> +++ b/testcases/kernel/syscalls/fanotify/fanotify25.c
> @@ -24,10 +24,10 @@ static const struct traceconfig {
>  	const char *filename;
>  	const char *wdata;
>  } trace_cmds[] = {
> -	{EVENTS_SYSFILE, "p:ltp_load_module_0 load_module"},
> -	{MNTPOINT "/events/kprobes/ltp_load_module_0/enable", "1"},
> -	{MNTPOINT "/events/kprobes/ltp_load_module_0/enable", "0"},
> -	{EVENTS_SYSFILE, "-:ltp_load_module_0"},
> +	{EVENTS_SYSFILE, "p:ltp_load_script_0 load_script"},
> +	{MNTPOINT "/events/kprobes/ltp_load_script_0/enable", "1"},
> +	{MNTPOINT "/events/kprobes/ltp_load_script_0/enable", "0"},
> +	{EVENTS_SYSFILE, "-:ltp_load_script_0"},

Doesn't this depend on CONFIG_BINFMT_SCRIPT? How likely is that this is
turned off?

If possible I would like to avoid whack-a-mole game trying to find
something that is commonly enabled.

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2026-03-02 15:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 14:44 [LTP] [PATCH] fanotify25: fix test failure on kernel with CONFIG_MODULES=n Amir Goldstein
2026-03-02 15:39 ` Cyril Hrubis [this message]
2026-03-02 17:07   ` Amir Goldstein
2026-03-03  8:52     ` Petr Vorel
2026-03-03  9:49     ` Martin Doucha
2026-03-03  9:54       ` Amir Goldstein
2026-03-03  9:59         ` Martin Doucha
2026-03-03 10:10           ` Amir Goldstein
2026-03-03 10:50             ` Martin Doucha
2026-03-03 11:31               ` Amir Goldstein
2026-03-02 16:44 ` Jan Kara

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=aaWvOIlfyIDH7J8A@yuki.lan \
    --to=chrubis@suse.cz \
    --cc=amir73il@gmail.com \
    --cc=jack@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox