Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp2160805ybm; Thu, 23 May 2019 12:21:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqxQ65NQtArlM6FtUDBm5WfXx6UpnV7ofhKZidULNO0RdspC+xJ1orBM8TiEVjyIYLEUkBa8 X-Received: by 2002:a17:902:b095:: with SMTP id p21mr48957270plr.270.1558639271535; Thu, 23 May 2019 12:21:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558639271; cv=none; d=google.com; s=arc-20160816; b=xVjq3/L2Hs+gImJR+taldIyEXcaju42OxFYH2Io1WR5d/B602x5x4fOVMEvEUpVfdU oxR1kkNgr+tKQy4FNOl2wkxnOFK5PwHRYb4VgvfiCNbpEJ3i5nVz0h3/sjzdSAMvPFP9 niGD2B8IN5ltgJQwXVpmVP7p1ktxO9t4n1dSYcVRVV191bTuak2ta6xtu78lAjrz3V1X qgawW6KhDTTK8JCpwYcn38qbTdn6/mn9ZtciOZ3QO100FbPkotE+PJk85CyLo0stZc39 8U+0L+ViSTfRAOSHU2fjDm+uwXfG/SPcHMwcgZ4JF/QIlmfybROQ/CToLsUEIO2eY0tw zxpg== 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=f5xzlivdvdoCH4Amt/TmL3U3gmuwY8/JX48Q3JEE22A=; b=ka8R7fPoexU9tQqd5eq1VRnIUe8oqXz4Sea2ptOQYWwi52Ron9Dz4NuMbSNUXxSdyr FgUxnnau3UYk+3hpozz3jk8NXnXhj0xWQvf+3A08BVORyOptbd3d3Qhzq77vimUIJz3z SVH3OAErpJurgIuGkP/836CYjSjL9uFpiucxB8TxaW0VZMcvhgBGmQTXwmiXlsfTuHRC 3L3umNiYvK3KQ2c3btIprkQ+Ud5yPKB7ONnjjyKoeP6PHBTvWDXyKhcXpSamiO2M4byk u0Kudv/ef1cK7fnnzKKGkfgdvrR86+cXWBgG69+NzzzlQ6kEHNqYoU0Re3KedxI2rVcA DvMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=xF+Ba1Et; 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 y26si289036pfe.165.2019.05.23.12.20.55; Thu, 23 May 2019 12:21:11 -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=xF+Ba1Et; 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 S2389812AbfEWTT0 (ORCPT + 99 others); Thu, 23 May 2019 15:19:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:55340 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389799AbfEWTTW (ORCPT ); Thu, 23 May 2019 15:19:22 -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 0CF032186A; Thu, 23 May 2019 19:19:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558639161; bh=pxM08Jm7nV5u+7Rp/rbVJR/+mOVGbPaQ4aZ/2Yp105I=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=xF+Ba1EtPNW7Yp9dZtR+EJlic3Q+s19PU5pS0JNHmhhRBcMnG2FUIChA32B9syHpR NU7HItqGk6ViNDW9Hf2mgq01nmzdGPZtaEanrimovFgfGDulGRiXJZxTCrs1ccFh8f CX4ORf7dWCeM2g6NWPWRjL0wUznWaRlIupk1yRTs= 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.19 109/114] md/raid: raid5 preserve the writeback action after the parity check Date: Thu, 23 May 2019 21:06:48 +0200 Message-Id: <20190523181740.700886331@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190523181731.372074275@linuxfoundation.org> References: <20190523181731.372074275@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 @@ -4185,7 +4185,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++; @@ -4210,6 +4210,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);