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 8A2BFC433F5 for ; Mon, 21 Feb 2022 23:36:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237050AbiBUXgl (ORCPT ); Mon, 21 Feb 2022 18:36:41 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:47604 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233290AbiBUXgk (ORCPT ); Mon, 21 Feb 2022 18:36:40 -0500 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8BB6525595 for ; Mon, 21 Feb 2022 15:36:16 -0800 (PST) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 3096621100; Mon, 21 Feb 2022 23:36:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1645486575; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XoPTsWGZsubWnpkaPgkDJ13wzvLVMLKE84KgUz1gWbQ=; b=uY58L9RSyZxZIkx4U+rfhjyw3JwomRIFJ31V9xY/5vTF3nagp5WiqKaA6tFHZGfBHYGacj F+LwYVow1k+EoHj2SS2fwvcBNBa2B+Wg8uET4cURNgihQRUh4CW6dKrif72IKf7jpw3c57 1SAjMpg3P1o7Vp8yN0+rQAlxVF2X+hk= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1645486575; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XoPTsWGZsubWnpkaPgkDJ13wzvLVMLKE84KgUz1gWbQ=; b=ni3aMEmh+FstaPmWShZRYVl9Rsjs6NX9NUuwyToyv3aNx+YB2DBhB5SXiCA4nXRO5NSWdT 0tAtR1mfvEu9oYBA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 7871613BA7; Mon, 21 Feb 2022 23:36:12 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id xJxkDewhFGInBgAAMHmgww (envelope-from ); Mon, 21 Feb 2022 23:36:12 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 From: "NeilBrown" To: "Peter Rajnoha" Cc: "Martin Wilck" , "Jes Sorensen" , linux-raid@vger.kernel.org, lvm-devel@redhat.com, "Hannes Reinecke" , "Heming Zhao" , "Coly Li" , dm-devel@redhat.com Subject: Re: [PATCH] udev-md-raid-assembly.rules: skip if DM_UDEV_DISABLE_OTHER_RULES_FLAG In-reply-to: <20220217130934.lh2b33255kyx2pax@alatyr-rpi.brq.redhat.com> References: <20220216205914.7575-1-mwilck@suse.com>, <164504936873.10228.7361167610237544463@noble.neil.brown.name>, , <20220217130934.lh2b33255kyx2pax@alatyr-rpi.brq.redhat.com> Date: Tue, 22 Feb 2022 10:36:05 +1100 Message-id: <164548656531.8827.3365536065813085321@noble.neil.brown.name> Precedence: bulk List-ID: X-Mailing-List: linux-raid@vger.kernel.org > The flags that DM use for udev were introduced before systemd project > even existed. We needed to introduce the DM_UDEV_DISABLE_OTHER_RULES_FLAG > to have a possibility for all the "other" (non-dm) udev rules to check > for if there's another subsystem stacking its own devices on top of DM > ones. If this is an established API that DM uses, then presumably it is documented somewhere. If a link to that documentation were provided, it would look a a whole lot less like a hack. Thanks, NeilBrown 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 us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 87B03C433F5 for ; Mon, 21 Feb 2022 23:38:31 +0000 (UTC) Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-483-eHQJ-BBPOAqjZoL_K_1w9A-1; Mon, 21 Feb 2022 18:38:26 -0500 X-MC-Unique: eHQJ-BBPOAqjZoL_K_1w9A-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 09C701006AA5; Mon, 21 Feb 2022 23:38:21 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id DE33F62D43; Mon, 21 Feb 2022 23:38:19 +0000 (UTC) Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 16D391809CAA; Mon, 21 Feb 2022 23:38:17 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id 21LNaMQ8002322 for ; Mon, 21 Feb 2022 18:36:22 -0500 Received: by smtp.corp.redhat.com (Postfix) id DDA842026D13; Mon, 21 Feb 2022 23:36:21 +0000 (UTC) Received: from mimecast-mx02.redhat.com (mimecast10.extmail.prod.ext.rdu2.redhat.com [10.11.55.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D88152026D60 for ; Mon, 21 Feb 2022 23:36:18 +0000 (UTC) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id DD8001C04B51 for ; Mon, 21 Feb 2022 23:36:18 +0000 (UTC) Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-373-ilKH_Rb9PnO3zZoCKfYPtw-1; Mon, 21 Feb 2022 18:36:17 -0500 X-MC-Unique: ilKH_Rb9PnO3zZoCKfYPtw-1 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 3096621100; Mon, 21 Feb 2022 23:36:15 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 7871613BA7; Mon, 21 Feb 2022 23:36:12 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id xJxkDewhFGInBgAAMHmgww (envelope-from ); Mon, 21 Feb 2022 23:36:12 +0000 MIME-Version: 1.0 From: "NeilBrown" To: "Peter Rajnoha" In-reply-to: <20220217130934.lh2b33255kyx2pax@alatyr-rpi.brq.redhat.com> References: <20220216205914.7575-1-mwilck@suse.com>, <164504936873.10228.7361167610237544463@noble.neil.brown.name>, , <20220217130934.lh2b33255kyx2pax@alatyr-rpi.brq.redhat.com> Date: Tue, 22 Feb 2022 10:36:05 +1100 Message-id: <164548656531.8827.3365536065813085321@noble.neil.brown.name> X-Mimecast-Impersonation-Protect: Policy=CLT - Impersonation Protection Definition; Similar Internal Domain=false; Similar Monitored External Domain=false; Custom External Domain=false; Mimecast External Domain=false; Newly Observed Domain=false; Internal User Name=false; Custom Display Name List=false; Reply-to Address Mismatch=false; Targeted Threat Dictionary=false; Mimecast Threat Dictionary=false; Custom Threat Dictionary=false X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 X-loop: dm-devel@redhat.com Cc: Jes Sorensen , Coly Li , lvm-devel@redhat.com, linux-raid@vger.kernel.org, dm-devel@redhat.com, Martin Wilck , Heming Zhao Subject: Re: [dm-devel] [PATCH] udev-md-raid-assembly.rules: skip if DM_UDEV_DISABLE_OTHER_RULES_FLAG X-BeenThere: dm-devel@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk List-Id: device-mapper development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dm-devel-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit > The flags that DM use for udev were introduced before systemd project > even existed. We needed to introduce the DM_UDEV_DISABLE_OTHER_RULES_FLAG > to have a possibility for all the "other" (non-dm) udev rules to check > for if there's another subsystem stacking its own devices on top of DM > ones. If this is an established API that DM uses, then presumably it is documented somewhere. If a link to that documentation were provided, it would look a a whole lot less like a hack. Thanks, NeilBrown -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel From mboxrd@z Thu Jan 1 00:00:00 1970 From: NeilBrown Date: Tue, 22 Feb 2022 10:36:05 +1100 Subject: [PATCH] udev-md-raid-assembly.rules: skip if DM_UDEV_DISABLE_OTHER_RULES_FLAG In-Reply-To: <20220217130934.lh2b33255kyx2pax@alatyr-rpi.brq.redhat.com> References: <20220216205914.7575-1-mwilck@suse.com>, <164504936873.10228.7361167610237544463@noble.neil.brown.name>, , <20220217130934.lh2b33255kyx2pax@alatyr-rpi.brq.redhat.com> Message-ID: <164548656531.8827.3365536065813085321@noble.neil.brown.name> List-Id: To: lvm-devel@redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit > The flags that DM use for udev were introduced before systemd project > even existed. We needed to introduce the DM_UDEV_DISABLE_OTHER_RULES_FLAG > to have a possibility for all the "other" (non-dm) udev rules to check > for if there's another subsystem stacking its own devices on top of DM > ones. If this is an established API that DM uses, then presumably it is documented somewhere. If a link to that documentation were provided, it would look a a whole lot less like a hack. Thanks, NeilBrown