From: Cyril Hrubis <chrubis@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH] API: Allow testing of kernel features in development
Date: Wed, 5 Jan 2022 16:57:04 +0100 [thread overview]
Message-ID: <YdW/0BUm+vBY3PHy@yuki> (raw)
In-Reply-To: <20211221113042.21357-1-rpalethorpe@suse.com>
Hi!
> Add an unstable kernel ABI flag and a runtest file for unstable
> tests. This means we can add tests which are likely to be broken by
> changes in the kernel ABI. Without disrupting LTP releases which are
> required to be stable.
>
> Users who require stability can filter the tests with this flag
> or not schedule the unstable runtest file(s).
>
> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
> ---
>
> How about adding this to the fanotify22 patch?
>
> include/tst_test.h | 12 ++++++++++++
> lib/tst_test.c | 6 ++++++
> runtest/syscalls-unstable | 3 +++
> 3 files changed, 21 insertions(+)
> create mode 100644 runtest/syscalls-unstable
>
> diff --git a/include/tst_test.h b/include/tst_test.h
> index 450ddf086..ff31e972e 100644
> --- a/include/tst_test.h
> +++ b/include/tst_test.h
> @@ -174,6 +174,18 @@ struct tst_test {
> int skip_in_lockdown:1;
> int skip_in_compat:1;
>
> + /*
> + * Test is for a feature that has not been added to the stable
> + * kernel ABI. That is, it's for a feature only available in
> + * linux-next, an RC or some other development branch.
> + *
> + * This string should be set to some text describing the
> + * kernel branch and version the test was developed
> + * against. e.g. "5.16 RC2", "linux-next-20211220",
> + * "net-next".
> + */
> + const char *const unstable_abi_version;
I would rather call this 'remove_after_release' or 'remove_after_kernel_release' but that is very minor.
> /*
> * The skip_filesystem is a NULL terminated list of filesystems the
> * test does not support. It can also be used to disable whole class of
> diff --git a/lib/tst_test.c b/lib/tst_test.c
> index 9b51bb5be..babb250d0 100644
> --- a/lib/tst_test.c
> +++ b/lib/tst_test.c
> @@ -1013,6 +1013,12 @@ static void do_setup(int argc, char *argv[])
> if (!tst_test)
> tst_brk(TBROK, "No tests to run");
>
> + if (tst_test->unstable_abi_version) {
> + tst_res(TINFO,
> + "This test was developed against pre-release kernel: %s",
> + tst_test->unstable_abi_version);
> + }
> +
> if (tst_test->tconf_msg)
> tst_brk(TCONF, "%s", tst_test->tconf_msg);
>
> diff --git a/runtest/syscalls-unstable b/runtest/syscalls-unstable
> new file mode 100644
> index 000000000..a87284afe
> --- /dev/null
> +++ b/runtest/syscalls-unstable
> @@ -0,0 +1,3 @@
> +# Tests for kernel features which are not finalized
> +
> +fanotify22 fanotify22
I would be even tempted to add this to the default syscalls runtest file
but render the test resultless, e.g. replace the tst_res() and tst_brk()
handlers in tst_res.c so that it will print only INFO messages.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-05 15:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211220180748.36A90A3B8E@relay2.suse.de>
2021-12-21 11:30 ` [LTP] [RFC PATCH] API: Allow testing of kernel features in development Richard Palethorpe via ltp
2021-12-21 12:14 ` Li Wang
2021-12-21 13:56 ` Richard Palethorpe
2021-12-21 17:56 ` Petr Vorel
2021-12-22 8:41 ` Jan Stancek
2021-12-22 8:44 ` Richard Palethorpe
2021-12-22 9:29 ` Petr Vorel
2022-01-05 15:57 ` Cyril Hrubis [this message]
2022-01-05 16:00 ` Cyril Hrubis
2022-01-10 8:09 ` Richard Palethorpe
2022-01-28 12:32 ` Petr Vorel
2022-02-03 10:18 ` [LTP] [PATCH] Create policy for testing unstable kernel features Richard Palethorpe via ltp
2022-02-03 10:22 ` Petr Vorel
2022-02-04 7:46 ` Jan Stancek
2022-02-08 8:18 ` Li Wang
2022-03-03 13:33 ` Petr Vorel
2022-06-14 12:31 ` Petr Vorel
2022-06-14 13:13 ` Cyril Hrubis
2022-06-16 8:25 ` 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=YdW/0BUm+vBY3PHy@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
/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