Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp2152403ybm; Thu, 23 May 2019 12:13:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqw6ZX+Q55ii3KoLjma/N+nBhTww/p9HGfyu1Yb5ue+bsnilP650J2aiydDwhZFL2rnesl0i X-Received: by 2002:a17:902:14e:: with SMTP id 72mr54629500plb.36.1558638802136; Thu, 23 May 2019 12:13:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558638802; cv=none; d=google.com; s=arc-20160816; b=hHKLR0gepqF4PikkKiWKBEWb2pZPeNytz1S9wNjGc9fW6MIfx8Jr03qf1wQIVQhZMj SZGWpTYERf7QUQefoBdnCmFzV4+UwXM98xsfzLqTAGbRnJTp0xiL0uz3aTKuAJrLvych iIdXgFF+u0sWoe+KSvUECZajU+zTYVrKErvozgUJHB/ap304pHKddHzqfawH308UVjmt HdfkjzXKEVJI3qx7Nvq7WWZXaBHCoUzIUUhiWGREB4JuOsHkcGBr2W52N3xc8SjjWEss bxewPFftI1ceP5RiU/TNdW28sNjt17mo8ipO65IB3simz3ZjcZGtiO2D9mOzk9LR6p4G PYyQ== 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=mbh9nzYaBjx2IYFMKY+aud+YFOs3zKDVAc3ZKZp7JBY=; b=C/JVVpXI7ibtBmylHY9f1lq0en8cGFUeVwqewmBBSQGgndeNum9Y9L8iiPKH4YXDn6 +CjBSNljqNOPrsNxizVx9zwfs1YBptQ9/e/OnSqqcGz+zLmwAN0s2xFl3ik9Ml3Yp5GK /lBWadVt1CieMW+lvclgk+jfLICq+fd/gi5/DsTO4bcGfQhgAeq9apCZ0/L6mgY1BStg qQzXCwlVtNAz22hRXqQGS95iIsxQyWR+MhdU17jwWodrSfy0mGaKgRP/hIbs8m5P79e/ tKnXnTKoBUEHNaitS3vBZziTG88ZiFNfKDS5O7n9kbCRy4+NM1sLcuFVlLfuTUeMZNqx v8fA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QwhrRzsN; 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 m15si305784pfh.46.2019.05.23.12.13.07; Thu, 23 May 2019 12:13:22 -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=QwhrRzsN; 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 S2387703AbfEWTKJ (ORCPT + 99 others); Thu, 23 May 2019 15:10:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:43440 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387650AbfEWTKI (ORCPT ); Thu, 23 May 2019 15:10:08 -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 9E0F5217F9; Thu, 23 May 2019 19:10:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558638608; bh=FZI5N1ooc/Jf6QBaLIZLSXt2/oMJG9xwKnO+Glubvng=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=QwhrRzsN6bkvLbUGIfM/wKPau60htNMJhAnKd/f0UEnF60c1piBhC4JGB3O9P1o/R w5J2seONfEYLTCRrAIggd8uQzgD8Fd5hBNH0dbhzGouDIXFhrY4ewV3c/d5cEuGtmg 7KSdFxmaeFFcI/+FThv6NYU3b5iQDOjnhPH38nOM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Dan Williams , Nigel Croxon , Song Liu Subject: [PATCH 4.9 52/53] md/raid: raid5 preserve the writeback action after the parity check Date: Thu, 23 May 2019 21:06:16 +0200 Message-Id: <20190523181719.226466348@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190523181710.981455400@linuxfoundation.org> References: <20190523181710.981455400@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: Nigel Croxon commit b2176a1dfb518d870ee073445d27055fea64dfb8 upstream. The problem is that any 'uptodate' vs 'disks' check is not precise in this path. Put a "WARN_ON(!test_bit(R5_UPTODATE, &dev->flags)" on the device that might try to kick off writes and then skip the action. Better to prevent the raid driver from taking unexpected action *and* keep the system alive vs killing the machine with BUG_ON. Note: fixed warning reported by kbuild test robot Signed-off-by: Dan Williams Signed-off-by: Nigel Croxon Signed-off-by: Song Liu Signed-off-by: Greg Kroah-Hartman --- drivers/md/raid5.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -3878,7 +3878,7 @@ static void handle_parity_checks6(struct /* now write out any block on a failed drive, * or P or Q if they were recomputed */ - BUG_ON(s->uptodate < disks - 1); /* We don't need Q to recover */ + dev = NULL; if (s->failed == 2) { dev = &sh->dev[s->failed_num[1]]; s->locked++; @@ -3903,6 +3903,14 @@ static void handle_parity_checks6(struct set_bit(R5_LOCKED, &dev->flags); set_bit(R5_Wantwrite, &dev->flags); } + if (WARN_ONCE(dev && !test_bit(R5_UPTODATE, &dev->flags), + "%s: disk%td not up to date\n", + mdname(conf->mddev), + dev - (struct r5dev *) &sh->dev)) { + clear_bit(R5_LOCKED, &dev->flags); + clear_bit(R5_Wantwrite, &dev->flags); + s->locked--; + } clear_bit(STRIPE_DEGRADED, &sh->state); set_bit(STRIPE_INSYNC, &sh->state);