diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2018-11-18 12:21:09 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-11-18 12:21:09 -0800 |
commit | 25e19c1fe421280a47f37c3571aa379e6e67966c (patch) | |
tree | 3635424070da53b33adcbd023657a6b8bcf805a5 /Makefile | |
parent | c67a98c00ea3c1fad14833f440fcd770232d24e7 (diff) | |
parent | 2121db09630113e67b51ae78c18115f1858f648a (diff) | |
download | talos-obmc-linux-25e19c1fe421280a47f37c3571aa379e6e67966c.tar.gz talos-obmc-linux-25e19c1fe421280a47f37c3571aa379e6e67966c.zip |
Merge tag 'libnvdimm-fixes-4.20-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
Pull libnvdimm fixes from Dan Williams:
"A small batch of fixes for v4.20-rc3.
The overflow continuation fix addresses something that has been broken
for several releases. Arguably it could wait even longer, but it's a
one line fix and this finishes the last of the known address range
scrub bug reports. The revert addresses a lockdep regression. The unit
tests are not critical to fix, but no reason to hold this fix back.
Summary:
- Address Range Scrub overflow continuation handling has been broken
since it was initially merged. It was only recently that error
injection and platform-BIOS support enabled this corner case to be
exercised.
- The recent attempt to provide more isolation for the kernel Address
Range Scrub state machine from userapace initiated sessions
triggers a lockdep report. Revert and try again at the next merge
window.
- Fix a kasan reported buffer overflow in libnvdimm unit test
infrastrucutre (nfit_test)"
* tag 'libnvdimm-fixes-4.20-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm:
Revert "acpi, nfit: Further restrict userspace ARS start requests"
acpi, nfit: Fix ARS overflow continuation
tools/testing/nvdimm: Fix the array size for dimm devices.
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions