Blame SOURCES/0001-Assemble-keep-MD_DISK_FAILFAST-and-MD_DISK_WRITEMOST.patch

5eacff
From 0833f9c3dbaaee202b92ea956f9e2decc7b9593a Mon Sep 17 00:00:00 2001
5eacff
From: Gioh Kim <gi-oh.kim@profitbricks.com>
5eacff
Date: Tue, 6 Nov 2018 15:27:42 +0100
5eacff
Subject: [RHEL7.7 PATCH 01/24] Assemble: keep MD_DISK_FAILFAST and
5eacff
 MD_DISK_WRITEMOSTLY flag
5eacff
5eacff
Before updating superblock of slave disks, desired_state value
5eacff
is set for the target state of the slave disks. But it forgets
5eacff
to check MD_DISK_FAILFAST and MD_DISK_WRITEMOSTLY flags. Then
5eacff
start_arrays() calls ADD_NEW_DISK ioctl-call and pass the state
5eacff
without MD_DISK_FAILFAST and MD_DISK_WRITEMOSTLY.
5eacff
5eacff
Currenlty it does not generate any problem because kernel does not
5eacff
care MD_DISK_FAILFAST or MD_DISK_WRITEMOSTLY flags.
5eacff
5eacff
Reviewed-by: NeilBrown <neilb@suse.com>
5eacff
Signed-off-by: Gioh Kim <gi-oh.kim@profitbricks.com>
5eacff
Signed-off-by: Jes Sorensen <jsorensen@fb.com>
5eacff
---
5eacff
 Assemble.c | 3 +++
5eacff
 1 file changed, 3 insertions(+)
5eacff
5eacff
diff --git a/Assemble.c b/Assemble.c
5eacff
index a79466c..f39c9e1 100644
5eacff
--- a/Assemble.c
5eacff
+++ b/Assemble.c
5eacff
@@ -1704,6 +1704,9 @@ try_again:
5eacff
 		else
5eacff
 			desired_state = (1<
5eacff
 
5eacff
+		desired_state |= devices[j].i.disk.state & ((1<
5eacff
+							    (1<
5eacff
+
5eacff
 		if (!devices[j].uptodate)
5eacff
 			continue;
5eacff
 
5eacff
-- 
5eacff
2.7.5
5eacff