From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5] Remove TODO
Date: Tue, 14 Oct 2025 11:22:50 +0200 [thread overview]
Message-ID: <aO4WanlsicVtKsSw@yuki.lan> (raw)
In-Reply-To: <20251014-remove_todo-v5-1-2793dffdec2d@suse.com>
Hi!
> diff --git a/doc/developers/todo.rst b/doc/developers/todo.rst
> new file mode 100644
> index 000000000..7daac7322
> --- /dev/null
> +++ b/doc/developers/todo.rst
> @@ -0,0 +1,75 @@
> +.. SPDX-License-Identifier: GPL-2.0-or-later
> +
> +List of ongoing tasks
> +=====================
> +
> +This is a comprehensive list of tasks where LTP maintainers are currently
> +working on. Priorities might change over time, but these are the most important
> +points which are currently being achieved.
> +
> +Fade out old tests runner
> +-------------------------
> +
> +:master:`runltp` script is old and unmaintaned. We are slowly shifting to
> +`kirk <https://github.com/linux-test-project/kirk>`_, that will be our official
> +tests runner in the next future.
^
Just: "in the future."
"next future" sounds like we are moving to a parallel reality or some
kind of scifi stuff.
> +kirk provides support for remote testing via Qemu, SSH, LTX, parallel
^
Kirk
> +execution and much more.
> +
> +Test new syscalls
> +-----------------
> +
> +Syscalls and new syscalls flags are added to Linux kernel each development
> +cycle and LTP still falls behind. Unfortunately there is no single place that
> +would store comprehensive list of syscalls, but there are a few places to look
> +at:
> +
> +- `man-pages repository <http://git.kernel.org/cgit/docs/man-pages/man-pages.git>`_
> + or the ``man2`` directory, where it's possible to find newly documented
> + functionalities.
> +- `LWN <http://lwn.net>`_ weekly editions.
> +- `linux-api mailing list <https://lore.kernel.org/linux-api/>`_ where
> + changes in kernel userspace API are discussed.
> +- `LTP Github issues <https://github.com/linux-test-project/ltp/issues>`_
> +
> +Rewrite old API tests
> +---------------------
> +
> +LTP has a long story and, at certain point of its development, new API were
> +introduced to make kernel testing easier and more efficient. This happened when
> +lots of tests were still using old, messy API.
> +
> +Some of these tests have been converted to the new API, but this process is
> +still ongoing for many others. To have an overview of the tests using old API,
> +please run the following command inside the LTP root folder:
> +
> +.. code-block:: bash
> +
> + git --no-pager grep -l 'include "test\.h"' testcases/
> +
> +Fade out shell scripts
> +----------------------
> +
> +LTP was initially thought as a generic framework for running tests with both
> +shell and plain-C languages. Even if writing tests in shell script might seem
> +easy, the reality is that debugging and maintaining certain test cases is
> +difficult and slow down the whole validation process. This is particularly
> +visible for cgroup tests, since shell doesn't add enough control over race
> +conditions.
> +
> +LTP maintainers are working on converting shell scripts to plain-C tests, in
> +order to reduce the impact that shell scripts might have on the overall kernel
> +testing.
> +
> +For a complete list of shell tests, please run the following command inside the
> +LTP root folder:
> +
> +.. code-block:: bash
> +
> + git --no-pager grep -l -e '^\. .*_lib\.sh' -e '^\. .*test.sh'
> +
> +LTP also provides a shell loader implementation for plain-C tests inside
> +:master:`testcases/lib/tst_run_shell.c` and it permits to run shell tests
> +into plain-C LTP API, featuring :ref:`struct tst_test` initializations and a
> +direct access to kernel syscalls.
Maybe we should link the (now empty) shell API page here:
https://linux-test-project.readthedocs.io/en/latest/developers/api_shell_tests.html
I plan to add the shell loader documentation there one day.
Otherwise it looks good to me, thanks for writing this.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-10-14 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 8:55 [LTP] [PATCH v5] Remove TODO Andrea Cervesato
2025-10-14 9:12 ` Li Wang via ltp
2025-10-14 9:22 ` Cyril Hrubis [this message]
2025-10-14 9:39 ` Andrea Cervesato via ltp
2025-10-14 11:00 ` Petr Vorel
2025-10-14 10:51 ` Petr Vorel
2025-10-14 11:16 ` Andrea Cervesato via ltp
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=aO4WanlsicVtKsSw@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.de \
--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.