From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5E374C001E0 for ; Thu, 10 Aug 2023 12:12:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234188AbjHJMMR (ORCPT ); Thu, 10 Aug 2023 08:12:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42924 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230335AbjHJMMQ (ORCPT ); Thu, 10 Aug 2023 08:12:16 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 70B671704 for ; Thu, 10 Aug 2023 05:11:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1691669495; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=TpYnbvJHiBn5GPlTGiJdN6VmHzW1BkIuCw6pPI/4rqY=; b=QMEDaB58JKkhUf9PcvWf05t/rPLb0BScRtRlIB05X1FxPJfx3467yu9PaVl+k/AxrLR/eG Xx1Ql9orfixkuJovaVB2fBiRMklp8l7GCMiq5KkjgMGlcxUmolM2rCFNh/ODJTUL2d5ddR ZUSRuUuDPZKf9T4JUGYexzfhv3nVsko= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-141-CzQVt2oYO0WOF0UNjydOeA-1; Thu, 10 Aug 2023 08:11:34 -0400 X-MC-Unique: CzQVt2oYO0WOF0UNjydOeA-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id D39D9101A528; Thu, 10 Aug 2023 12:11:33 +0000 (UTC) Received: from o.redhat.com (unknown [10.39.192.18]) by smtp.corp.redhat.com (Postfix) with ESMTP id 25D8640C2076; Thu, 10 Aug 2023 12:11:33 +0000 (UTC) From: heinzm@redhat.com To: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org Cc: ncroxon@redhat.com, xni@redhat.com Subject: [PATCH 0/3] md raid1: Fix writebehind/writemostly Date: Thu, 10 Aug 2023 14:11:29 +0200 Message-ID: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 Precedence: bulk List-ID: X-Mailing-List: linux-raid@vger.kernel.org From: heinzm Writemostly was only respected if set on the first leg. Set on any other leg(s) but not on the first one did not enable writebehind at all. Fix changes the logic using the already defind bool writebehind. Whilst on this, also make first_clone a bool as write_behind for consistency and add an empty line. Patches pass the MD test suite. heinzm (3): md raid1: allow writebehind to work on any leg device set WriteMostly md raid1: make first_clone a bool md raid1: add empty line Signed-off-by: Heinz Mauelshagen Tested-by: Xia Ni drivers/md/raid1.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) -- 2.41.0