kernel/drivers/nvdimm/badrange.c, branch linux-5.1.yHosts the 0x221E linux distro kernel.https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-5.1.y2017-11-02T17:42:30Zlibnvdimm, badrange: remove a WARN for list_empty2017-11-02T17:42:30ZVishal Vermavishal.l.verma@intel.com2017-10-30T20:22:21Zurn:sha1:89360b87c3efa5d265a3b43dd8fc245c8f4356e3
Now that we're reusing the badrange functions for nfit_test, and that
exposes badrange injection/clearing to userspace via the DSM paths, it
is plausible that a user may call the clear DSM multiple times. Since it
is harmless to do so, we can remove the WARN in badrange_forget.
Cc: Dave Jiang <dave.jiang@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>
libnvdimm: move poison list functions to a new 'badrange' file2017-11-02T17:42:30ZDave Jiangdave.jiang@intel.com2017-08-23T19:48:26Zurn:sha1:aa9ad44a42b4cf4387f8ecddaf8e51707fdcda5a
nfit_test needs to use the poison list manipulation code as well. Make
it more generic and in the process rename poison to badrange, and move
all the related helpers to a new file.
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
[vishal: Add badrange.o to nfit_test's Kbuild]
[vishal: add a missed include in bus.c for the new badrange functions]
[vishal: rename all instances of 'be' to 'bre']
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>