Dan Williams

I believe this should be addressed by the blanket update to create-namespace error reporting that is already pending for v68: https://lore.kernel.org/linux-nvdimm/158300764577.2141307.437568876961580865.stgit@dwillia2-desk3.amr.corp.intel.com/

@stellarhopper but for cases where cxl_test is missing we need to skip, not fail i.e.: ``` diff --git a/test/cxl-create-region.sh b/test/cxl-create-region.sh index 8e297caf6a0d..aae180dd7b54 100644 --- a/test/cxl-create-region.sh +++ b/test/cxl-create-region.sh @@ -4,7 +4,7...

Hmm, yes, I think it would make sense to move the firmware-update.sh test to the "destructive" set since it affects the host system: ``` diff --git a/test/meson.build b/test/meson.build index 5953c286d13f..c31d8eac66c5...

nfit_test depends on replacing the "production" version of the drivers/nvdimm/ modules with the ones that tools/testing/nvdimm/Kbuild creates. Likely what is happening is that you have, for example, the original libnvdimm.ko...

I wonder if this patch fixes it: [patch.txt](https://github.com/pmem/ndctl/files/10147543/patch.txt) ...i.e. that the problem arises from mixing int64 and uint64 json-c APIs. Otherwise it's likely too late to create that ABI breakage...

What is missing for me for this issue and many others in this project is what is the threat model, impact, and alternative mitigations? The major alternative mitigation for any...

> The threat model is here: https://elixir.bootlin.com/linux/latest/source/Documentation/security/snp-tdx-threat-model.rst If smth is missing in your opinion, please shout, we can add/update it. That threat model was taken up by the PCI SIG....

another option, if the nfit-test dependency on cxl is problematic, is to perhaps use memmap= to replace what efi_fake_mem was doing: `memmap=%-+` Just need to be careful that unlike efi_fake_mem...

@yizhanglinux I believe this test assumes that the NVDIMM under test supports namespace labels. To be clear this test suite is meant to be run against canned configurations from QEMU,...

> That looks reasonable, both the nvdimm-n and intel nvdimm have the "provider":"ACPI.NFIT", is there a way to distinguish them? If so, we can update the tests to skip on...