path: root/tools/testing/nvdimm
diff options
authorDan Williams <dan.j.williams@intel.com>2017-09-26 11:41:28 -0700
committerDan Williams <dan.j.williams@intel.com>2017-09-28 09:13:06 -0700
commitb18d4b8a25af6fe83d7692191d6ff962ea611c4f (patch)
tree5bdcb887f2b09d3a5110a3468f35df799eaf6e32 /tools/testing/nvdimm
parentlibnvdimm, pfn: make 'resource' attribute only readable by root (diff)
libnvdimm, namespace: fix label initialization to use valid seq numbers
The set of valid sequence numbers is {1,2,3}. The specification indicates that an implementation should consider 0 a sign of a critical error: UEFI 2.7: 13.19 NVDIMM Label Protocol Software never writes the sequence number 00, so a correctly check-summed Index Block with this sequence number probably indicates a critical error. When software discovers this case it treats it as an invalid Index Block indication. While the expectation is that the invalid block is just thrown away, the Robustness Principle says we should fix this to make both sequence numbers valid. Fixes: f524bf271a5c ("libnvdimm: write pmem label set") Cc: <stable@vger.kernel.org> Reported-by: Juston Li <juston.li@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'tools/testing/nvdimm')
0 files changed, 0 insertions, 0 deletions