summaryrefslogtreecommitdiffstats
path: root/block/Kconfig
diff options
context:
space:
mode:
authorVishal Verma <vishal.l.verma@intel.com>2017-05-10 15:01:31 -0600
committerDan Williams <dan.j.williams@intel.com>2017-05-10 21:46:22 -0700
commitb177fe85dd27de1ee4c29f59c4e82b3ea3b78784 (patch)
treefe0b38a554197181de1f019a14893c83201d7bb1 /block/Kconfig
parent3ae3d67ba705c754a3c91ac009f9ce73a0e7286a (diff)
downloadlinux-0-day-b177fe85dd27de1ee4c29f59c4e82b3ea3b78784.tar.gz
linux-0-day-b177fe85dd27de1ee4c29f59c4e82b3ea3b78784.tar.xz
libnvdimm, btt: ensure that initializing metadata clears poison
If we had badblocks/poison in the metadata area of a BTT, recreating the BTT would not clear the poison in all cases, notably the flog area. This is because rw_bytes will only clear errors if the request being sent down is 512B aligned and sized. Make sure that when writing the map and info blocks, the rw_bytes being sent are of the correct size/alignment. For the flog, instead of doing the smaller log_entry writes only, first do a 'wipe' of the entire area by writing zeroes in large enough chunks so that errors get cleared. Cc: Andy Rudoff <andy.rudoff@intel.com> Cc: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'block/Kconfig')
0 files changed, 0 insertions, 0 deletions