|author||Vishal Verma <email@example.com>||Thu Feb 18 12:02:37 2021 -0700|
|committer||Vishal Verma <firstname.lastname@example.org>||Thu Feb 18 17:42:05 2021 -0700|
test/libcxl: introduce a command size fuzzing test Add a new test within test/libcxl which tries different combinations of valid and invalid payload sizes, and ensures that the kernel responds as expected by either succeeding, erroring out the ioctl, adjusting the out.size in the response etc. The fuzz set is a statically defined array which contains the different combinations to test. Adding a new combination onle needs appending to this array. Signed-off-by: Vishal Verma <email@example.com>
Utility library for managing the libnvdimm (non-volatile memory device) sub-system in the Linux kernel
./autogen.sh ./configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib64 make make check sudo make install
There are a number of packages required for the build steps that may not be installed by default. For information about the required packages, see the “BuildRequires:” lines in ndctl.spec.in.
See the latest documentation for the NVDIMM kernel sub-system here:
A getting started guide is also available on the kernel.org nvdimm wiki:
The unit tests run by
make check require the nfit_test.ko module to be loaded. To build and install nfit_test.ko:
Obtain the kernel source. For example,
git clone -b libnvdimm-for-next git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git
Skip to step 3 if the kernel version is >= v4.8. Otherwise, for kernel versions < v4.8, configure the kernel to make some memory available to CMA (contiguous memory allocator). This will be used to emulate DAX.
cma=200M on the kernel command line.
Compile the libnvdimm sub-system as a module, make sure “zone device” memory is enabled, and enable the btt, pfn, and dax features of the sub-system:
CONFIG_X86_PMEM_LEGACY=m CONFIG_ZONE_DEVICE=y CONFIG_LIBNVDIMM=m CONFIG_BLK_DEV_PMEM=m CONFIG_ND_BLK=m CONFIG_BTT=y CONFIG_NVDIMM_PFN=y CONFIG_NVDIMM_DAX=y CONFIG_DEV_DAX_PMEM=m CONFIG_ENCRYPTED_KEYS=y
Build and install the unit test enabled libnvdimm modules in the following order. The unit test modules need to be in place prior to the
depmod that runs during the final
make M=tools/testing/nvdimm sudo make M=tools/testing/nvdimm modules_install sudo make modules_install
make check in the ndctl source directory, or
ndctl test, if ndctl was built with
The unit tests will validate that the environment is set up correctly before they try to run. If the platform is misconfigured, i.e. the unit test modules are not available, or the test versions of the modules are superseded by the “in-tree/production” version of the modules
make check will skip tests and report a message like the following in test/test-suite.log:
SKIP: libndctl ============== test/init: nfit_test_init: nfit.ko: appears to be production version: /lib/modules/4.8.8-200.fc24.x86_64/kernel/drivers/acpi/nfit/nfit.ko.xz __test_skip: explicit skip test_libndctl:2684 nfit_test unavailable skipping tests
If the unit test modules are indeed available in the modules ‘extra’ directory the default depmod policy can be overridden by adding a file to /etc/depmod.d with the following contents:
override nfit * extra override device_dax * extra override dax_pmem * extra override dax_pmem_core * extra override dax_pmem_compat * extra override libnvdimm * extra override nd_blk * extra override nd_btt * extra override nd_e820 * extra override nd_pmem * extra
The nfit_test module emulates pmem with memory allocated via vmalloc(). One of the side effects is that this breaks ‘physically contiguous’ assumptions in the driver. Use the '--align=4K option to ‘ndctl create-namespace’ to avoid these corner case scenarios.