RE: Question about ndctl unit tests

[Qi, Fuli]

> -Original Message-
> From: Dan Williams [mailto:dan.j.willi...@intel.com]
> Sent: Sunday, July 1, 2018 3:12 AM
> To: Qi, Fuli/斉 福利 
> Cc: linux-nvdimm@lists.01.org; Verma, Vishal L ; 
> Mizuma,
> Masayoshi/水間 理仁 ; Gotou, Yasunori/五島 康文
> 
> Subject: Re: Question about ndctl unit tests
> 
> On Sat, Jun 30, 2018 at 1:07 AM, Qi, Fuli  wrote:
> > Hi,
> >
> >
> >
> > When I ran the unit tests, I found "libndctl" and "dsm-fail" cannot
> > pass the test.
> 
> Yes, sorry, we recently reworked some tests. Grab our work-in-progress kernel 
> branch
> here:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git
> libnvdimm-pending
> 
> This will move to nvdimm/nvdimm.git libnvdimm-for-next in the coming weeks 
> for 4.19.
> 
> You'll also want to grab:
> 
> https://patchwork.kernel.org/patch/10495297/
> 
> ...for the error handling tests. This will appear on github.com/pmem/ndctl 
> master
> soon.

OK, I see.
Thank you very much.
Qi
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

Re: Question about ndctl unit tests

[Dan Williams]

On Sat, Jun 30, 2018 at 1:07 AM, Qi, Fuli  wrote:
> Hi,
>
>
>
> When I ran the unit tests, I found "libndctl" and "dsm-fail" cannot pass the
> test.

Yes, sorry, we recently reworked some tests. Grab our work-in-progress
kernel branch here:

git://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git
libnvdimm-pending

This will move to nvdimm/nvdimm.git libnvdimm-for-next in the coming
weeks for 4.19.

You'll also want to grab:

https://patchwork.kernel.org/patch/10495297/

...for the error handling tests. This will appear on
github.com/pmem/ndctl master soon.
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

Question about ndctl unit tests

[Qi, Fuli]

Hi,

When I ran the unit tests, I found "libndctl" and "dsm-fail" cannot pass the 
test.
Here is the test log.

# less test/libndctl.log
libkmod: kmod_module_remove_module: could not remove 'nfit_test': No such file 
or directory
check_set_config_data: dimm: 0 read2 data miscompare: 0
check_set_config_data: dimm: 0x1 read2 data miscompare: 0
check_set_config_data: dimm: 0x100 read2 data miscompare: 0
check_set_config_data: dimm: 0x101 read2 data miscompare: 0
check_dax_autodetect: dax_ndns: 0x1049f10 ndns: 0x1049f10
namespace1.0: expected write_cache enabled
check_namespaces: namespace1.0 validate_write_cache failed
ndctl-test0 failed: -6
libkmod: kmod_module_remove_module: could not remove 'nfit_test': Resource 
temporarily unavailable
libdaxctl: daxctl_unref: context 0x1038170 released
libndctl: ndctl_unref: context 0x1039290 released
FAIL libndctl (exit status: 1)

# less test/dsm-fail.log
victim: nmem0
validate_namespace_options:571: region1: falling back to a 4K alignment
validate_namespace_options:571: region1: falling back to a 4K alignment
do_test:294
libndctl: ndctl_dimm_enable: nmem0: failed to enable
fail expected nmem0 enable success victim: nmem0 rc: -6
libkmod: kmod_module_remove_module: could not remove 'nfit_test': Resource 
temporarily unavailable
libdaxctl: daxctl_unref: context 0x89f170 released
libndctl: ndctl_unref: context 0x8a0290 released
{
  "dev":"namespace1.0",
  "mode":"raw",
  "size":4194304,
  "uuid":"9a07ca1d-54cd-4252-b87e-475b24af8a1c",
  "sector_size":512,
  "blockdev":"pmem1"
}
{
  "dev":"namespace1.1",
  "mode":"raw",
  "size":4194304,
  "uuid":"2eb40a75-5c5f-4ed9-b36e-4fd0abba7783",
  "sector_size":512,
  "blockdev":"pmem1.1"
}
FAIL dsm-fail (exit status: 250)

And my kernel version:
$ uname -a
Linux 4.18.0-rc2+ #25 SMP

I guess the reason is that the nfit_test module cannot be removed.
# modprobe -r nfit_test
modprobe: FATAL: Module nfit_test is in use.
# lsmod | grep nfit_test
nfit_test  40960  8
nd_pmem20480  1 nfit_test
nfit   65536  1 nfit_test
device_dax 20480  2 dax_pmem,nfit_test
libnvdimm 163840  7 
dax_pmem,nfit_test,nd_btt,nd_pmem,nd_e820,nd_blk,nfit
nfit_test_iomap20480  6 
dax_pmem,nfit_test,device_dax,nd_pmem,libnvdimm,nfit

Does anyone know how to fix it?

Thank you very much.
QI
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm