diff options
author | Dan Williams <dan.j.williams@intel.com> | 2017-04-29 15:24:03 -0700 |
---|---|---|
committer | Dan Williams <dan.j.williams@intel.com> | 2017-04-29 15:24:03 -0700 |
commit | 23f4984483623cf8621246004228f08fcabf51e4 (patch) | |
tree | 4545eac73213e6c22a2c43af64818db1e7023aa0 /include/media/v4l2-async.h | |
parent | 7699a6a36b82f22cb0b355c6411531abedf12964 (diff) | |
download | linux-23f4984483623cf8621246004228f08fcabf51e4.tar.gz linux-23f4984483623cf8621246004228f08fcabf51e4.tar.bz2 linux-23f4984483623cf8621246004228f08fcabf51e4.zip |
libnvdimm: rework region badblocks clearing
Toshi noticed that the new support for a region-level badblocks missed
the case where errors are cleared due to BTT I/O.
An initial attempt to fix this ran into a "sleeping while atomic"
warning due to taking the nvdimm_bus_lock() in the BTT I/O path to
satisfy the locking requirements of __nvdimm_bus_badblocks_clear().
However, that lock is not needed since we are not acting on any data that
is subject to change under that lock. The badblocks instance has its own
internal lock to handle mutations of the error list.
So, in order to make it clear that we are just acting on region devices,
rename __nvdimm_bus_badblocks_clear() to nvdimm_clear_badblocks_regions().
Eliminate the lock and consolidate all support routines for the new
nvdimm_account_cleared_poison() in drivers/nvdimm/bus.c. Finally, to the
opportunity to cleanup to some unnecessary casts, make the calling
convention of nvdimm_clear_badblocks_regions() clearer by replacing struct
resource with the minimal struct clear_badblocks_context, and use the
DEVICE_ATTR macro.
Cc: Dave Jiang <dave.jiang@intel.com>
Cc: Vishal Verma <vishal.l.verma@intel.com>
Reported-by: Toshi Kani <toshi.kani@hpe.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'include/media/v4l2-async.h')
0 files changed, 0 insertions, 0 deletions