Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp27364ybp; Thu, 3 Oct 2019 09:42:26 -0700 (PDT) X-Google-Smtp-Source: APXvYqxsQgoI1FuTe9k1guu+zlqXxsOVkdr+e6TSRaFjm+7htP9zUbKw87awt11QWafQiXN2vq/U X-Received: by 2002:a17:906:80c3:: with SMTP id a3mr8388691ejx.271.1570120946759; Thu, 03 Oct 2019 09:42:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570120946; cv=none; d=google.com; s=arc-20160816; b=O9JtgCrv5vrcm9iqL6CCxQJhJNad7m3Y6Gf8zzW4BFvCRwNozU1qMNrcaxf62+ZhUF Gvy4Rzqkg48Jg5NKUYn50EC3VSRV/D5+4w6NCtb9O6G/im7RoCGcteUTzILC0qXaYqCG Jvhnfef9KfqSrE1SLYSaKSHrbFSqEUhCSAOYthbFsEphiyX3mPPsxMiPgl956nEElKp2 QX22E1HZN+w5d1SpqiGRNGBFwDw28fPsnOBJaRaynoabQ55YN/RpZ7NutjjG4IGy83dU /ISJWilbvSuBMe18rR60t7trmH1hwN15+kDPWFn3eTNzrEakegeOUZlYSOwNeSBTT4b2 rgUw== 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=d0wDPzttYoR4dh2/m7/QbY0iip0gewr/WSqjNg5EjLo=; b=QIUaliOhLAb6/bvgv1cEpB14EuJu8IoCwTBEmGXlgqSMHdlczEIjEdi0/Zw6qCdUbq l49muJ/MzxeMvHxMLFEo/MJXV+tpqv7iECXbi3nzEtC08IaZ0AAYH2EUUrRAYYGbsUXf 2ZeLk7bfAehlzgblYpM9vZcjhV3SqT3CM7F56bIrLB5GcC90PVy29Ri9Jm31VVbuDY79 i0louVsJ5J3mKP6mGgXWe5wXZToBwoBqB7+lhCh3GfsZrWdirkLyN6N3tiIA+8re7cDL JdzDqfgFhge93uTTsmRKhKpSc7zpbJhR/Gul3qvzqu+u3O2IUe/Eduo9GzOHTLgxqjp8 2wLA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=dj3ZYgT4; 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 v25si1945288edb.286.2019.10.03.09.42.01; Thu, 03 Oct 2019 09:42:26 -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=dj3ZYgT4; 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 S2392309AbfJCQiY (ORCPT + 99 others); Thu, 3 Oct 2019 12:38:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:48076 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2392144AbfJCQiX (ORCPT ); Thu, 3 Oct 2019 12:38:23 -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 D3ACC20830; Thu, 3 Oct 2019 16:38:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570120702; bh=apEfD4q9zyhxqB3xsHAa2NQ+UoWoYJIDYz+hdQ4OCN4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=dj3ZYgT4JvZBA69e3qoZv+2DV15m5ZWNui8pG1Ap3563UvmotZscqQxyfTKbKyPEc Fdb7U3fj5TiE6xOJBTq36beRLSSmEvkPFbrXm5vfB8RWVdthKtyHY+ZcxbuJdvewte gSEH6GySlVVUPtQ2vU4DvGokHoTCNJifTZ6//2Fw= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Xiao Ni , Song Liu Subject: [PATCH 5.2 292/313] md/raid6: Set R5_ReadError when there is read failure on parity disk Date: Thu, 3 Oct 2019 17:54:30 +0200 Message-Id: <20191003154601.901780807@linuxfoundation.org> X-Mailer: git-send-email 2.23.0 In-Reply-To: <20191003154533.590915454@linuxfoundation.org> References: <20191003154533.590915454@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 @@ -2559,7 +2559,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