From: "Michal Suchánek" <msuchanek@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux NVDIMM <nvdimm@lists.linux.dev>
Subject: Re: ndctl tests usable?
Date: Tue, 26 Apr 2022 20:09:58 +0200 [thread overview]
Message-ID: <20220426180958.GJ163591@kunlun.suse.cz> (raw)
In-Reply-To: <CAPcyv4jUj3v+4Sf=1i5EjxTeX9Ur65Smib-vkuaBdKYjUrh7yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
On Tue, Apr 26, 2022 at 09:47:19AM -0700, Dan Williams wrote:
> On Tue, Apr 26, 2022 at 9:43 AM Michal Suchánek <msuchanek@suse.de> wrote:
> >
> > On Tue, Apr 26, 2022 at 09:32:24AM -0700, Dan Williams wrote:
> > > On Tue, Apr 26, 2022 at 9:15 AM Michal Suchánek <msuchanek@suse.de> wrote:
> > > >
> > > > On Tue, Apr 26, 2022 at 08:51:25AM -0700, Dan Williams wrote:
> > > > > On Tue, Apr 26, 2022 at 5:39 AM Michal Suchánek <msuchanek@suse.de> wrote:
> > > > > >
...
> > >
> > > The modinfo just tells you what modules are available, but it does not
> > > necessarily indicate which modules are actively loaded in the system
> > > which is what ndctl_test_init() validates.
> >
> > Isn't what modinfo lists also what modrobe loads?
>
> It shows what modprobe would load on the next invocation, but
> sometimes when nfit_test fails it's because the initramfs or something
> else loaded the modules without respecting the extra/ (or updates/ in
> your case) override modules.
>
> > There isn't any pmem so I don't see why production modules would be
> > loaded before the test modules are installed. Unloading the modules
> > first does not really make any difference.
>
> Ok, my first guess was wrong... would need more debug to see what
> those other skip tests are complaining about.
There was also missing parted and hostname command.
However, the nfit.ko is detected as production even when I remove all
the production modules just in case. lsmod confirms that the nvdimm
modules are not loaded before the test.
Maybe something goes wrong with the test module build?
It is very fragile and requires complete kernel source for each
configuration built. See below for the package
https://build.opensuse.org/package/show/home:michals/nfit_test
Attaching the log of test run which does not report any missing tools,
only complains about nfit.ko being production.
Thanks
Michal
[-- Attachment #2: ndctl-test.log.xz --]
[-- Type: application/x-xz, Size: 28232 bytes --]
next prev parent reply other threads:[~2022-04-26 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 12:38 Michal Suchánek
2022-04-26 15:51 ` Dan Williams
2022-04-26 16:14 ` Michal Suchánek
2022-04-26 16:32 ` Dan Williams
2022-04-26 16:38 ` Michal Suchánek
2022-04-26 16:47 ` Dan Williams
2022-04-26 18:09 ` Michal Suchánek [this message]
2022-04-26 18:22 ` Dan Williams
2022-04-27 11:26 ` Michal Suchánek
2022-04-28 4:32 ` Shivaprasad G Bhat
2022-04-28 8:51 ` Michal Suchánek
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=20220426180958.GJ163591@kunlun.suse.cz \
--to=msuchanek@suse.de \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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
all inboxes | Powered by JetHome®