From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] lib: Check minimal supported kernel version
Date: Fri, 4 Sep 2026 11:51:55 +0200 [thread overview]
Message-ID: <20260904095155.GB1206368@pevik> (raw)
In-Reply-To: <apqNcb103ZVuzpIf@yuki.lan>
> Hi!
> > LTP does not support kernels older than 4.4, but this requirement was
> > only documented in static text without automated runtime validation.
> > Define the minimal supported kernel version in tst_kvercmp.h so that
> > the documentation fetches it dynamically and the core library aborts
> > unsupported kernels with TCONF during test setup.
> Great idea, but I wouldn't tst_brk() on older kernels, I would just
> print a message that there may be failures becuase older kernels are not
> supported or tested.
Yes, exactly, tst_brk() is way too aggressive. tst_res(TINFO) is good enough
to give the information without deliberately break all the tests.
> LTP has been historically used for many different purposes, e.g. for
> testing BSD compatibility layout for running Linux binaries and I fear
> that hard stop on older kernel versions would break these usecases.
+1.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-09-04 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 8:07 [LTP] [PATCH] lib: Check minimal supported kernel version Andrea Cervesato
2026-09-04 9:20 ` [LTP] " linuxtestproject.agent
2026-09-04 9:20 ` [LTP] [PATCH] " Cyril Hrubis
2026-09-04 9:25 ` Andrea Cervesato via ltp
2026-09-04 9:51 ` Petr Vorel [this message]
2026-09-07 8:32 ` Kubaj, Piotr
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=20260904095155.GB1206368@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@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 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.