Skip to content

Commit 4eaaa2b

Browse files
committed
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
2 parents d089709 + ffe81d4 commit 4eaaa2b

File tree

2 files changed

+26
-1
lines changed

2 files changed

+26
-1
lines changed

block/blk-mq.c

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1715,6 +1715,15 @@ static blk_status_t __blk_mq_issue_directly(struct blk_mq_hw_ctx *hctx,
17151715
break;
17161716
case BLK_STS_RESOURCE:
17171717
case BLK_STS_DEV_RESOURCE:
1718+
/*
1719+
* If direct dispatch fails, we cannot allow any merging on
1720+
* this IO. Drivers (like SCSI) may have set up permanent state
1721+
* for this request, like SG tables and mappings, and if we
1722+
* merge to it later on then we'll still only do IO to the
1723+
* original part.
1724+
*/
1725+
rq->cmd_flags |= REQ_NOMERGE;
1726+
17181727
blk_mq_update_dispatch_busy(hctx, true);
17191728
__blk_mq_requeue_request(rq);
17201729
break;
@@ -1727,6 +1736,18 @@ static blk_status_t __blk_mq_issue_directly(struct blk_mq_hw_ctx *hctx,
17271736
return ret;
17281737
}
17291738

1739+
/*
1740+
* Don't allow direct dispatch of anything but regular reads/writes,
1741+
* as some of the other commands can potentially share request space
1742+
* with data we need for the IO scheduler. If we attempt a direct dispatch
1743+
* on those and fail, we can't safely add it to the scheduler afterwards
1744+
* without potentially overwriting data that the driver has already written.
1745+
*/
1746+
static bool blk_rq_can_direct_dispatch(struct request *rq)
1747+
{
1748+
return req_op(rq) == REQ_OP_READ || req_op(rq) == REQ_OP_WRITE;
1749+
}
1750+
17301751
static blk_status_t __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,
17311752
struct request *rq,
17321753
blk_qc_t *cookie,
@@ -1748,7 +1769,7 @@ static blk_status_t __blk_mq_try_issue_directly(struct blk_mq_hw_ctx *hctx,
17481769
goto insert;
17491770
}
17501771

1751-
if (q->elevator && !bypass_insert)
1772+
if (!blk_rq_can_direct_dispatch(rq) || (q->elevator && !bypass_insert))
17521773
goto insert;
17531774

17541775
if (!blk_mq_get_dispatch_budget(hctx))
@@ -1810,6 +1831,9 @@ void blk_mq_try_issue_list_directly(struct blk_mq_hw_ctx *hctx,
18101831
struct request *rq = list_first_entry(list, struct request,
18111832
queuelist);
18121833

1834+
if (!blk_rq_can_direct_dispatch(rq))
1835+
break;
1836+
18131837
list_del_init(&rq->queuelist);
18141838
ret = blk_mq_request_issue_directly(rq);
18151839
if (ret != BLK_STS_OK) {

drivers/ata/libata-core.c

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4602,6 +4602,7 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
46024602
{ "SSD*INTEL*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
46034603
{ "Samsung*SSD*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
46044604
{ "SAMSUNG*SSD*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
4605+
{ "SAMSUNG*MZ7KM*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
46054606
{ "ST[1248][0248]0[FH]*", NULL, ATA_HORKAGE_ZERO_AFTER_TRIM, },
46064607

46074608
/*

0 commit comments

Comments
 (0)