Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp572316ybn; Thu, 3 Oct 2019 09:02:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqzVBRm1/rArMUpr4oAfXHKN08eXudmC5KcjOZdC9M0Qpsr+HBncSnmlXqqKK7HSQAmobFLL X-Received: by 2002:a50:f09d:: with SMTP id v29mr10184589edl.4.1570118569759; Thu, 03 Oct 2019 09:02:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570118569; cv=none; d=google.com; s=arc-20160816; b=Qp4SNtdNatle8PjoAuWJGugD47r2P2D2TYLKMEYhntQTgf3oM/QwZDEuuEgvIp7qwj rPYoOfNjCyrPPZ3XOW1lLD+3dphHHNOC+FbS/h4cExDD+1EX6Ts9oasF+BBpSjOu/3kK rmkW90h1ByHefkUT7UHPTVEz7zletkpKa7MfTXF9KKC0Z/4LWuRWPe0lG+IjaXlTfNwo zi2BYCPbexThGmWNOBLeIILha1EF/ryZxABrDR8G49lTXHcMGG+W9Hxt7Zi8mJpktOTf 9sGgHAqs0X5n/taY+fyFbKx7RFWBf+qO1xcVZuowhLuOLk2aB4j5KjpnvAsTpcFWkB2P SggQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=jmmeSGpfVCvSTvIgUoe7mqodmyWjhxPCydt9bOWTdAw=; b=cwqZIlMI3zIaE7V1Qu6CAOc/+n+VJxAf77IC1bqD2IkEhe15p73dSEuNqRDCV3JfCe 4qXkjfCNhAGpP1WRvTAHw0Y+LIFXPv1MHeg89P4cTfzSapqqk72iZvB7Hyz6r1vXHvvY wbIzUVXZuFsYEshKP8Aa7FuRJ2xKxME2SMfCeIRJAXzNut1nCmRwJmd+wcwV33uCwjfg sTNCmrzXQQl2qvFgChWpsvwdviruqBwrsSyvVwCKNJhYx7FQqH1+hTMCFTHaRzF/YvID NXXlguL1NdXI/VJdhlGGVmz2g4Vl8LdPRRpOz17NvvQDfpi39DAljJM+cb5QoFiOGkD1 Sltw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=cTdZ13qk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x19si1426236eju.15.2019.10.03.09.02.23; Thu, 03 Oct 2019 09:02:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=cTdZ13qk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729880AbfJCQAT (ORCPT + 99 others); Thu, 3 Oct 2019 12:00:19 -0400 Received: from mail.kernel.org ([198.145.29.99]:43944 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729732AbfJCQAQ (ORCPT ); Thu, 3 Oct 2019 12:00:16 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9541F20830; Thu, 3 Oct 2019 16:00:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570118416; bh=dAwhzUaKbLdSeqMT5ZJ1TQUKNfFgFh1FT2Ze30/BIdA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=cTdZ13qkPM/amZbL9miQvvbpDTqXjZZxDxN9sTSWzfjU9mSIAG2A0KsJyMulvi6b9 ooTuNUjsaMDouARHxswq31BUB8mkQ1qI96lJ2SvnnQATyMr5Y8QzSzoW0eT+5H2xAB E5TTM0aikiRw5Qnc7bSumjuNqQarpQ6IkH2WXorU= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Xiao Ni , Song Liu Subject: [PATCH 4.4 88/99] md/raid6: Set R5_ReadError when there is read failure on parity disk Date: Thu, 3 Oct 2019 17:53:51 +0200 Message-Id: <20191003154338.656585846@linuxfoundation.org> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20191003154252.297991283@linuxfoundation.org> References: <20191003154252.297991283@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Xiao Ni commit 143f6e733b73051cd22dcb80951c6c929da413ce upstream. 7471fb77ce4d ("md/raid6: Fix anomily when recovering a single device in RAID6.") avoids rereading P when it can be computed from other members. However, this misses the chance to re-write the right data to P. This patch sets R5_ReadError if the re-read fails. Also, when re-read is skipped, we also missed the chance to reset rdev->read_errors to 0. It can fail the disk when there are many read errors on P member disk (other disks don't have read error) V2: upper layer read request don't read parity/Q data. So there is no need to consider such situation. This is Reported-by: kbuild test robot Fixes: 7471fb77ce4d ("md/raid6: Fix anomily when recovering a single device in RAID6.") Cc: #4.4+ Signed-off-by: Xiao Ni Signed-off-by: Song Liu Signed-off-by: Greg Kroah-Hartman --- drivers/md/raid5.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -2394,7 +2394,9 @@ static void raid5_end_read_request(struc && !test_bit(R5_ReadNoMerge, &sh->dev[i].flags)) retry = 1; if (retry) - if (test_bit(R5_ReadNoMerge, &sh->dev[i].flags)) { + if (sh->qd_idx >= 0 && sh->pd_idx == i) + set_bit(R5_ReadError, &sh->dev[i].flags); + else if (test_bit(R5_ReadNoMerge, &sh->dev[i].flags)) { set_bit(R5_ReadError, &sh->dev[i].flags); clear_bit(R5_ReadNoMerge, &sh->dev[i].flags); } else