linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Cc: lucas.demarchi@intel.com, linux-modules@vger.kernel.org
Subject: Re: [PATCH kmod] testsuite: add tests for weak dependencies
Date: Mon, 8 Jul 2024 15:58:03 +0100	[thread overview]
Message-ID: <Zov-e-a_KQyJb8LI@arch-x395> (raw)
In-Reply-To: <20240530070836.9438-1-jtornosm@redhat.com>

Hello Jose,

On 2024/05/30, Jose Ignacio Tornos Martinez wrote:
> The following tests to verify weak dependencies have been implemented:
> 1) modprobe test to check that related weakdep modules are not loaded
>    due to being a weakdep.
> 2) depmod test to check weakdep output.
> 3) user test to check that configuration files with weakdep are parsed
>    correctly and related weakdep modules can be read correctly from user
>    applications.
> 
> Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
> ---

Seems like this commit has regressed make distcheck on my end. Namely
I'm running the following commands:

git clone ...
cd kmod
git clean -fxd
./autogen.sh c
make distcheck

Result in:

...
make[5]: *** No rule to make target '.../kmod-32/_build/sub/testsuite/module-playground/mod-weakdep.o', needed by '.../kmod-32/_build/sub/testsuite/module-playground/mod-weakdep.mod'.  Stop.
make[4]: *** [Makefile:1903: .../kmod-32/_build/sub/testsuite/module-playground] Error 2


Can you reproduce it on your end?


While in the area, a couple of question if I may:

- Should we move the new weakdeps API in libkmod/libkmod.sym near the
  end in a separate LIBKMOD_XX section?

As-is, it looks like we're adding symbols to what should be a frozen set
(aka LIBKMOD_5, which was released decade+ ago).

Admittedly there was a similar erroneous(?) change not loo long ago -
9becaae ("libkmod: Add lookup from module name").

@Lucas can/should we fix the kmod_module_new_from_name_lookup symbol in
the version script?


- Is this work related to the weak-modules used in RHEL/Fedora [1]?
  Alternatively, would the RedHat team consider having the weak-modules
  solution in upstream kmod?

... assuming Lucas is OK with the idea. I'm approaching with with my
dkms co-maintainer hat on, where the fewer "if distro == X" logic we
have the better.

Thanks in advance,
Emil

[1] https://src.fedoraproject.org/rpms/kmod/blob/rawhide/f/weak-modules

  parent reply	other threads:[~2024-07-08 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30  7:08 [PATCH kmod] testsuite: add tests for weak dependencies Jose Ignacio Tornos Martinez
2024-06-14 19:17 ` Lucas De Marchi
2024-07-08 14:58 ` Emil Velikov [this message]
2024-07-09  5:11   ` Lucas De Marchi
2024-07-09  7:45     ` Jose Ignacio Tornos Martinez

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=Zov-e-a_KQyJb8LI@arch-x395 \
    --to=emil.l.velikov@gmail.com \
    --cc=jtornosm@redhat.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.demarchi@intel.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;
as well as URLs for NNTP newsgroup(s).