summaryrefslogtreecommitdiffstats
path: root/mm/kasan
diff options
context:
space:
mode:
authorDan Williams <dan.j.williams@intel.com>2017-05-01 10:00:02 -0700
committerDan Williams <dan.j.williams@intel.com>2017-05-01 10:00:02 -0700
commita3e9af95f794d000debc2a5ba3186ba85a6e115f (patch)
tree2450d68251fd90f469ca0a91e3ade228ca63f1b9 /mm/kasan
parent452bae0aede774f87bf56c28b6dd50b72c78986c (diff)
downloadlinux-stable-a3e9af95f794d000debc2a5ba3186ba85a6e115f.tar.gz
linux-stable-a3e9af95f794d000debc2a5ba3186ba85a6e115f.tar.bz2
linux-stable-a3e9af95f794d000debc2a5ba3186ba85a6e115f.zip
libnvdimm: restore "libnvdimm: band aid btt vs clear poison locking"
This continues the 4.11 status quo of disabling of error clearing from the BTT I/O path. Toshi found that even though we have eliminated all the libnvdimm sources of sleeping-while-atomic triggers, we still have sleeping operations that will occur in the path to send the ACPI DSM to the DIMM to clear the error: BUG: sleeping function called from invalid context at mm/slab.h:432 in_atomic(): 1, irqs_disabled(): 0, pid: 13353, name: dd Call Trace: dump_stack+0x86/0xc3 ___might_sleep+0x17d/0x250 __might_sleep+0x4a/0x80 __kmalloc+0x1c0/0x2e0 acpi_os_allocate_zeroed+0x2d/0x2f acpi_evaluate_object+0x59/0x3b1 acpi_evaluate_dsm+0xbd/0x10c acpi_nfit_ctl+0x1ef/0x7c0 [nfit] ? nsio_rw_bytes+0x152/0x280 nvdimm_clear_poison+0x77/0x140 nsio_rw_bytes+0x18f/0x280 btt_write_pg+0x1d4/0x3d0 [nd_btt] btt_make_request+0x119/0x2d0 [nd_btt] A solution for tracking and handling media errors natively in the BTT is needed. Cc: Jeff Moyer <jmoyer@redhat.com> 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 'mm/kasan')
0 files changed, 0 insertions, 0 deletions