Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp8091ybp; Thu, 3 Oct 2019 09:26:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqyuJWClbmnGPrAlUgvyOCEMWEwAhuQjk3uc4InVhXbxUDXzGkBT4k/MV9ETd7xrFEpftD6k X-Received: by 2002:a05:6402:651:: with SMTP id u17mr10659565edx.104.1570119962070; Thu, 03 Oct 2019 09:26:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570119962; cv=none; d=google.com; s=arc-20160816; b=nBQbOzatqTi524I1No72LZXWmIoMRj/vvgHbQcgX5jytHWHEWQz4x8UGmP8jSwkDeR 5ZbTxEBkO3RYZmrhUkPzvn+z7wdQhDryxgxZVZE+UgFQY1AYO45nmPuAIjjtWfo4FY6u SnbX3jw+ptforDOtzoZuWgVNTUpSdP6fIhl/uTzKZI0RRzJXpq3Nk+LtC0VNnDTPOg40 MGtGSlwBZlO2PcwkQOPK7uxzRBh5zGQ9dNc+y3jaCZZPmhGUlm3NZ0MBAjbT+f5fKADq 1TTznY1tDpfQc0bdlM0rhrIbuTqwkX5/HHBWJuqEqP1PK9QNnebhZprZbpgJDWacZL8y Xxpg== 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=T4yTkya8GLqZhIhJKTb8gis1skfCgyqhAyAtFIhKk0I=; b=aIWk0mWEL3uVxgseGfAO3o7sxroZjE9y9H1siRrD2XQVq1/qACtj2BvBSGRZ37Wik8 iKB9nJtrJAIvfY7tOPjn9PWxkBM5fID+byBWxmAOBHwhGF4ZP2+yIIOiGwSM/JsSgJbN EYoAIb99xvbCFx0geHJlBMbsOFDztreV1wOVzfxTYPx1RubgWmcIaxADON5sFxX2+PQe kInez0BxTUglQpMlA2Q6ZB4jeL5kz7cwseQlQOPtuhrNrTF7BrDIiIuq98r9tKX/VDGx q1DYDBbyZpf/ZgoMtHLStCt+jUblwYgUQ5YUFdh16pjAz9kTcxmdBAlwk6t0790XKJGj kZ2Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=FYCr+e1N; 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 v6si1762296edw.51.2019.10.03.09.25.37; Thu, 03 Oct 2019 09:26:02 -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=FYCr+e1N; 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 S2388984AbfJCQYD (ORCPT + 99 others); Thu, 3 Oct 2019 12:24:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:53422 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390666AbfJCQYA (ORCPT ); Thu, 3 Oct 2019 12:24:00 -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 3381E2054F; Thu, 3 Oct 2019 16:23:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570119839; bh=+rMBaEag7aAOupdKm7Bl3aOSwArtbmDVv/fbkQoEaok=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=FYCr+e1N3HpnTHdFMTe0ZToaWI5V2Nq8tDOTj9jTWCWohsLTA/aq8pWcJUZz9Blh9 MDx+B65cWB9DUF2rzR3+r5M4Z7k/f9nBE3ZLyLJbIEvMw7yMotDoLdPRJ2XKpuhgXU yACV+XPjNl8hTsh4S60GXHzNdd6qd5++o24Qp59E= 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.19 196/211] md/raid6: Set R5_ReadError when there is read failure on parity disk Date: Thu, 3 Oct 2019 17:54:22 +0200 Message-Id: <20191003154529.214835592@linuxfoundation.org> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20191003154447.010950442@linuxfoundation.org> References: <20191003154447.010950442@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 @@ -2573,7 +2573,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