All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <li.wang@linux.dev>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 1/4] lib: add module is loaded check
Date: Wed, 14 Oct 2026 11:18:27 +0800	[thread overview]
Message-ID: <as70g8dWFN1ZF4Ph@linux.dev> (raw)
In-Reply-To: <oxUvYO8wV14vdPyltlLgB09i0ZBYZcJfi9qY@localhost.localdomain>

Hi Andrea,

> Hi Li,
> 
> > +
> > +bool tst_module_is_loaded(const char *mod_name)
> > +{
> > +	char line[4096];
> > +	size_t mod_len = strlen(mod_name);
> > +	FILE *file;
> > +
> > +	file = fopen("/proc/modules", "r");
> > +	if (!file)
> > +		return false;
> 
> why not using SAFE_FILE_LINES_SCANF() ?

file_lines_scanf() uses a fixed format string, and with
`arg_count == 0` (e.g. `"%s %*s"` with only suppressed
conversions) it cannot distinguish a matching line from a
non-matching one, because vsscanf returns 0 in both cases.

On top of that, /proc/modules needs to walk every line and
compare against a module name that is passed in at runtime
and may need the '-' to '_' normalization. So it is not a
good fit here; a plain fopen()/fgets() loop is clearer.

One more concern: /proc/modules may not exist at all on some
platforms. When the kernel is built with CONFIG_MODULES=n
there is no module support and /proc/modules is absent, and
some container runtimes also do not provide it. With that
would trigger tst_brkm(TBROK) and abort the test

-- 
Regards,
Li Wang

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

  reply	other threads:[~2026-10-14  3:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10  3:36 [LTP] [PATCH v3 0/4] tst_kconfig: automatic module load/unload for CONFIG_*=m Li Wang
2026-10-10  3:36 ` [LTP] [PATCH v3 1/4] lib: add module is loaded check Li Wang
2026-10-10  9:38   ` [LTP] " linuxtestproject.agent
2026-10-12 15:48   ` [LTP] [PATCH v3 1/4] " Andrea Cervesato via ltp
2026-10-14  3:18     ` Li Wang [this message]
2026-10-10  3:36 ` [LTP] [PATCH v3 2/4] tst_kconfig: load and unload kernel modules for CONFIG_*=m Li Wang
2026-10-12 16:09   ` Andrea Cervesato via ltp
2026-10-14  3:36     ` Li Wang
2026-10-10  3:36 ` [LTP] [PATCH v3 3/4] tst_kconfig: add module mappings for vsock/vsock_loopback Li Wang
2026-10-12 15:51   ` Andrea Cervesato via ltp
2026-10-14  3:43     ` Li Wang
2026-10-14  5:01     ` Li Wang
2026-10-14  7:13       ` Andrea Cervesato via ltp
2026-10-10  3:36 ` [LTP] [PATCH v3 4/4] testcases: drop manual tst_modprobe() now handled by tst_kconfig Li Wang

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=as70g8dWFN1ZF4Ph@linux.dev \
    --to=li.wang@linux.dev \
    --cc=andrea.cervesato@suse.com \
    --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.