summaryrefslogtreecommitdiffstats
path: root/mm
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2018-12-05 22:28:01 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2018-12-05 22:28:01 +0100
commit4eaaa2b99e30305f4bc677f4abfe56c1f8b39670 (patch)
treef31de7aced04f268aa6ccd429c81ba4d880aded5 /mm
parentMerge tag 'for-4.20-rc5-tag' of git://git.kernel.org/pub/scm/linux/kernel/git... (diff)
parentblk-mq: fix corruption with direct issue (diff)
downloadlinux-4eaaa2b99e30305f4bc677f4abfe56c1f8b39670.tar.xz
linux-4eaaa2b99e30305f4bc677f4abfe56c1f8b39670.zip
Merge tag 'for-linus-20181205' of git://git.kernel.dk/linux-block
Pull block fixes from Jens Axboe: "A bit earlier in the week as usual, but there's a fix here that should go in sooner rather than later. Under a combination of circumstance, the direct issue path in blk-mq could corrupt data. This wasn't easy to hit, but the ones that are affected by it, seem to hit it pretty easily. Full explanation in the patch. None of the regular filesystem and storage testing has triggered it, even though it's been around since 4.19-rc1. Outside of that, whitelist trim tweak for certain Samsung devices for libata" * tag 'for-linus-20181205' of git://git.kernel.dk/linux-block: blk-mq: fix corruption with direct issue libata: whitelist all SAMSUNG MZ7KM* solid-state disks
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions