From: Petr Mladek <pmladek@suse.com>
To: Marcos Paulo de Souza <mpdesouza@suse.com>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Joe Lawrence <joe.lawrence@redhat.com>
Subject: Re: [linux-next:master 1016/2825] make[2]: *** kselftest/livepatch/test_modules: No such file or directory. Stop.
Date: Wed, 31 Jan 2024 16:34:22 +0100 [thread overview]
Message-ID: <ZbpnBqHUl3pE_3Te@alley> (raw)
In-Reply-To: <ed54875555c282ad3b09503020a7aa978a80bd60.camel@suse.com>
On Tue 2024-01-30 11:39:56, Marcos Paulo de Souza wrote:
> On Tue, 2024-01-30 at 07:08 +0800, kernel test robot wrote:
> > tree:
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git m
> > aster
> > head: 596764183be8ebb13352b281a442a1f1151c9b06
> > commit: c4bbe83d27c2446a033cc0381c3fb6be5e8c41c7 [1016/2825]
> > livepatch: Move tests from lib/livepatch to selftests/livepatch
> > compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> > reproduce (this is a W=1 build):
> > (https://download.01.org/0day-ci/archive/20240130/202401300736.GkSZoS
> > rA-lkp@intel.com/reproduce)
> >
> When looking at the lib.mk, I just followed the other variables and did
> the same:
>
> TEST_GEN_MODS_DIR := $(patsubst %,$(OUTPUT)/%,$(TEST_GEN_MODS_DIR))
>
> But later on, I jump into $(TEST_GEN_MODS_DIR), which is invalid
> because of the O= that is used a prefix for the path:
> /tmp/kselftest/kselftest/livepatch/test_modules. My first idea was to
> just remove the patsubst and take TEST_GEN_MODS_DIR, which should be
> livepatch/test_modules in this case, but it then returns another
> problem:
>
>
> make: Entering directory
> '/home/mpdesouza/git/linux/tools/testing/selftests'
> make[1]: Entering directory
> '/home/mpdesouza/git/linux/tools/testing/selftests/livepatch'
> make -C test_modules
> make[2]: Entering directory
> '/home/mpdesouza/git/linux/tools/testing/selftests/livepatch/test_modul
>
> es'
> make -C /lib/modules/6.5.9-1-default/build modules
> KBUILD_EXTMOD=/home/mpdesouza/git/linux/tools/testing/selftests/livepat
>
> ch/test_modules
Nit: There are sometimes strange empty lines between split long
lines. It looks like somehow messed cut&paste.
> make[3]: Entering directory '/usr/src/linux-6.5.9-1-obj/x86_64/default'
> make[4]: Entering directory '/tmp/kselftest'
> /usr/src/linux-6.5.9-1/Makefile:754: include/config/auto.conf: No such
> file or directory
I see the same. It looks to me like a bug in kernel-devel package.
/usr/src/linux-6.5.9-1/Makefile is from the kernel-devel package
for the running kernel. It should try to include auto.conf used
for building the running kernel:
1. auto.conf should be packaged in kernel-devel.
2. The Makefile from the kernel-devel packages should be able
to find/use auto.conf from the kernel-devel package.
IMHO, this actually helped to find a bug that
make -C tools/testing/selftests/livepatch used auto.conf from
the git tree while the modules are built against headers
for the running kernel.
That said, I wonder why this problem does not happen when building
external modules (KMPs). I would expect that they are using
the same Makefile from the kernel-devel package.
Maybe the external modules somehow manage to clear "need-config"
used by /usr/src/linux-6.5.9-1/Makefile. Maybe we do not need
to include it either.
> make[4]: *** [/usr/src/linux-6.5.9-1/Makefile:234: __sub-make] Error 2
> make[4]: Leaving directory '/tmp/kselftest'
> make[3]: *** [../../../linux-6.5.9-1/Makefile:234: __sub-make] Error 2
> make[3]: Leaving directory '/usr/src/linux-6.5.9-1-obj/x86_64/default'
> make[2]: *** [Makefile:16: modules] Error 2
> make[2]: Leaving directory
> '/home/mpdesouza/git/linux/tools/testing/selftests/livepatch/test_modul
>
> es'
> make[1]: *** [../lib.mk:92: gen_mods_dir] Error 2
> make[1]: Leaving directory
> '/home/mpdesouza/git/linux/tools/testing/selftests/livepatch'
> make: *** [Makefile:180: all] Error 2
> make: Leaving directory
> '/home/mpdesouza/git/linux/tools/testing/selftests'
Best Regards,
Petr
next prev parent reply other threads:[~2024-01-31 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 23:08 [linux-next:master 1016/2825] make[2]: *** kselftest/livepatch/test_modules: No such file or directory. Stop kernel test robot
2024-01-30 14:39 ` Marcos Paulo de Souza
2024-01-31 15:34 ` Petr Mladek [this message]
2024-01-31 18:39 ` Marcos Paulo de Souza
2024-01-31 18:40 ` Marcos Paulo de Souza
2024-02-05 18:05 ` Marcos Paulo de Souza
2024-02-14 14:27 ` Marcos Paulo de Souza
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=ZbpnBqHUl3pE_3Te@alley \
--to=pmladek@suse.com \
--cc=joe.lawrence@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mpdesouza@suse.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
/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).