Commit 89360b87 authored by Vishal Verma's avatar Vishal Verma Committed by Dan Williams

libnvdimm, badrange: remove a WARN for list_empty

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: default avatarVishal Verma <vishal.l.verma@intel.com>
Signed-off-by: default avatarDan Williams <dan.j.williams@intel.com>
parent 9fb1a190
...@@ -114,7 +114,6 @@ void badrange_forget(struct badrange *badrange, phys_addr_t start, ...@@ -114,7 +114,6 @@ void badrange_forget(struct badrange *badrange, phys_addr_t start,
struct badrange_entry *bre, *next; struct badrange_entry *bre, *next;
spin_lock(&badrange->lock); spin_lock(&badrange->lock);
WARN_ON_ONCE(list_empty(badrange_list));
/* /*
* [start, clr_end] is the badrange interval being cleared. * [start, clr_end] is the badrange interval being cleared.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment