public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Li Wang via ltp <ltp@lists.linux.it>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] lib: tst_kconfig: Add runtime checks
Date: Fri, 27 Mar 2026 15:02:48 +0800	[thread overview]
Message-ID: <acYrmGE0yu07rJsn@redhat.com> (raw)
In-Reply-To: <20260326144006.3035-1-chrubis@suse.cz>

> So far for CONFIG_*_NS.

It would be great to have a description for the feature:

Something maybe like:

 "Currently, LTP Kconfig parsing logic only checks if a feature was
  enabled during kernel compilation (e.g., CONFIG_USER_NS=y). However,
  some kernel features can be compiled in but disabled at runtime via
  kernel command-line parameter or sysctls. When this happens, tests
  relying on these Kconfig variables attempt to run and fail, rather
  than being gracefully skipped.
  
  This patch introduces a runtime check mechanism for Kconfig variables.
  When a monitored CONFIG_* variable is parsed as 'y' or 'm', the framework
  now executes an associated runtime check function. If the runtime check
  fails, the framework logs an info message and internally overrides the
  variable's state to 'n'. This allows the existing LTP dependency logic
  to properly skip tests that require the disabled feature."

Also, add test_kconfig04.c in newlib_tests/ to verify this works?

-- 
Regards,
Li Wang


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

  parent reply	other threads:[~2026-03-27  7:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 14:40 [LTP] [PATCH] lib: tst_kconfig: Add runtime checks Cyril Hrubis
2026-03-26 15:15 ` Petr Vorel
2026-03-27  7:02 ` Li Wang via ltp [this message]
2026-03-27 11:06   ` Cyril Hrubis
  -- strict thread matches above, loose matches on Subject: below --
2026-02-05 13:57 Cyril Hrubis
2026-02-05 17:47 ` Petr Vorel
2026-02-06  7:58   ` Li Wang via ltp
2026-02-06  8:23     ` Petr Vorel
2026-02-06 12:23       ` Li Wang via ltp
2026-03-26 14:09         ` Cyril Hrubis
2026-03-26 14:16           ` Cyril Hrubis
2026-03-26 16:39           ` Petr Vorel
2026-02-06  8:23     ` Petr Vorel
2026-02-06  8:33     ` Cyril Hrubis
2026-02-06  9:31       ` Petr Vorel
2026-02-06  9:37       ` Petr Vorel
2026-02-06  9:45         ` Cyril Hrubis
2026-02-06 10:31           ` Petr Vorel
2026-03-26 14:38   ` Cyril Hrubis
2026-03-26 15:44     ` Petr Vorel
2026-03-11  8:59 ` Petr Vorel
2026-03-24  8:33 ` Andrea Cervesato via ltp
2026-03-26 14:17   ` 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=acYrmGE0yu07rJsn@redhat.com \
    --to=ltp@lists.linux.it \
    --cc=chrubis@suse.cz \
    --cc=liwang@redhat.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