libnvdimm: add an atomic vs process context flag to rw_bytes

Browse source

nsio_rw_bytes can clear media errors, but this cannot be done while we
are in an atomic context due to locking within ACPI. From the BTT,
->rw_bytes may be called either from atomic or process context depending
on whether the calls happen during initialization or during IO.

During init, we want to ensure error clearing happens, and the flag
marking process context allows nsio_rw_bytes to do that. When called
during IO, we're in atomic context, and error clearing can be skipped.

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>

...

This commit is contained in:

Vishal Verma 2017-05-10 15:01:30 -06:00 • committed by Dan Williams

parent 8376efd31d

commit 3ae3d67ba7

7 changed files with 53 additions and 42 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

drivers/nvdimm/blk.c

View file

67

drivers/nvdimm/btt.c

View file

2

drivers/nvdimm/btt_devs.c

View file

6

drivers/nvdimm/claim.c

View file

1

drivers/nvdimm/nd.h

View file

4

drivers/nvdimm/pfn_devs.c

View file

12

include/linux/nd.h

View file