[dm-devel] [PATCH] fix nvme test
Mikulas Patocka
mpatocka at redhat.com
Mon Feb 26 20:22:32 UTC 2018
Hi
The strncmp function should compare 4 bytes.
But I'm wondering what's the purpose of this test at all? bio-based
interface doesn't support partial completions for any device - so why do
we need special code path just for nvme and why can't we use it for other
block devices?
Mikulas
Signed-off-by: Mikulas Patocka <mpatocka at redhat.com>
---
drivers/md/dm-table.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/drivers/md/dm-table.c
===================================================================
--- linux-2.6.orig/drivers/md/dm-table.c 2018-02-24 03:40:18.000000000 +0100
+++ linux-2.6/drivers/md/dm-table.c 2018-02-26 19:36:29.728499000 +0100
@@ -1755,7 +1755,7 @@ static int device_no_partial_completion(
char b[BDEVNAME_SIZE];
/* For now, NVMe devices are the only devices of this class */
- return (strncmp(bdevname(dev->bdev, b), "nvme", 3) == 0);
+ return (strncmp(bdevname(dev->bdev, b), "nvme", 4) == 0);
}
static bool dm_table_does_not_support_partial_completion(struct dm_table *t)
More information about the dm-devel
mailing list