Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp9047850rwd; Wed, 21 Jun 2023 02:12:53 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ43pV3/CYXvs2AphK+EWKeejGmi4u7hgGsN6E7gSy4nRdrkKLo4nHY5S6MH6tGWXZ0B+g73 X-Received: by 2002:a05:6a00:35ca:b0:662:3de1:2861 with SMTP id dc10-20020a056a0035ca00b006623de12861mr26999423pfb.6.1687338773404; Wed, 21 Jun 2023 02:12:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687338773; cv=none; d=google.com; s=arc-20160816; b=EndANqloRkSmn8ueTNEC1KiUrp/xXxYaUGEgW7gT7Qt0YThRWl8xD/yGyepv4vPYK1 ZLgvJm4Run5cXOC68dPj0SrCXFKjE95Fhlfb2e9JulU0YF8//DJL1i9JEDiat4KE+7Z8 hB7iVLfyzJOznaJwp7NIV+303qiMdfEx6cyQtPUnAY4Gt0uvOHONt2kRCPeq8rdBcDMW lfFhmj2B9bgrWsSTcvQb//BWTbv7enCYZkBE0D3WDMhIt1ULar9ntCj4YgZ8Bbc0tRHi VdU1WoHEljWm0m46tKg5yV52FhL3kSh8Ev6HTGmF8FDRMTWNluyf9P7JhY8NW/iF94JX Feyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=C7PPqDZAmzcbcg0rWIZX01hC1JN4/nlDeRusA0hxj38=; b=wGW+o7jFym82phQWf7SVG28y/6EznJJ5gVpA5RKT0wHw4hqYUHVmKwL0m77gfZ8Q+q RuSNHNHmzDmpCHXn6u/5d6UbCc3QAk2zhEJ2LuWs0G/DAWne/6PKw4sMhplVnJWJHMDQ HLUWy7GM5ZwJzKw1r+jaGKAx2R7BdrKOK7iBXqJRdRRaKs9ovwKH3/vHgv0ayobdv51v EjTa+SU66mFjE1ohj5yNCUepYTJUyh013OsRODw1wNlSsXtFHkxjhXL8lNQCPVbEMeoE zxH4apN21LnKLLiaKwZG2A3P9CmIFgQe5LIyQVXuLoficrg/yGyQ+OkZ1R0bKsOk6pRT Ci8A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=PVbKK07w; dkim=neutral (no key) header.i=@suse.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v6-20020a626106000000b0066874e0802csi3612247pfb.145.2023.06.21.02.12.39; Wed, 21 Jun 2023 02:12:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=PVbKK07w; dkim=neutral (no key) header.i=@suse.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230428AbjFUJC4 (ORCPT + 99 others); Wed, 21 Jun 2023 05:02:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45266 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230417AbjFUJC1 (ORCPT ); Wed, 21 Jun 2023 05:02:27 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0EA6F19B7; Wed, 21 Jun 2023 02:02:26 -0700 (PDT) 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 B93C221A44; Wed, 21 Jun 2023 09:02:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1687338144; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=C7PPqDZAmzcbcg0rWIZX01hC1JN4/nlDeRusA0hxj38=; b=PVbKK07wbYQLl7N/k95ONxfqybkfrZz3Sd26AdMOljQkkvKs23hIY62UaiM9Yy+Qngxl8n yBiRGjeD0Jc/PbHIpI7bTatZKg8TksnWrmoErbcArSB4teDzgJAE1hYXZhmw0ttzZsMsqi SYGYLE3S4HqNGpkY0m9LMBJFvxE5uGo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1687338144; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=C7PPqDZAmzcbcg0rWIZX01hC1JN4/nlDeRusA0hxj38=; b=2dZQ1LcBI9BComcRh1bGM2eti1X2u0XXMJpg/eBfRfeZmpsO4M+ZXDu7K9iLxfuT+1wVK4 yrxg3tEzF7/qjICw== 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 AAA31134B1; Wed, 21 Jun 2023 09:02:24 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id WzqeKaC8kmQrZAAAMHmgww (envelope-from ); Wed, 21 Jun 2023 09:02:24 +0000 Date: Wed, 21 Jun 2023 11:02:24 +0200 From: Daniel Wagner To: Sagi Grimberg Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, Chaitanya Kulkarni , Shin'ichiro Kawasaki , Hannes Reinecke , James Smart , Martin Belanger Subject: Re: [PATCH blktests v1 2/3] nvme/rc: Avoid triggering host nvme-cli autoconnect Message-ID: References: <20230620132703.20648-1-dwagner@suse.de> <20230620132703.20648-3-dwagner@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 20, 2023 at 07:43:35PM +0200, Daniel Wagner wrote: > On Tue, Jun 20, 2023 at 05:07:43PM +0300, Sagi Grimberg wrote: > > Hmm... is this hapenning with non-fc as well? > > I haven't seen a problem for TCP or RDMA yet but in principle it should also > exists. I can do some tracing to see if we have also problem thern. Two of the > udev rule match on the subsystem and the event type. The only udev rule which gets triggered during blktests execution is this one: # nvme-fc transport generated events (old-style for compatibility) ACTION=="change", SUBSYSTEM=="fc", ENV{FC_EVENT}=="nvmediscovery", \ ENV{NVMEFC_HOST_TRADDR}=="*", ENV{NVMEFC_TRADDR}=="*", \ RUN+="@SYSTEMCTL@ --no-block restart nvmf-connect@--device=none\t--transport=fc\t--traddr=$env{NVMEFC_TRADDR}\t--trsvcid=none\t--host-traddr=$env{NVMEFC_HOST_TRADDR}.service" That explain why blktests didn't get disturbed by the autoconnect rule as this rule has a match on the fc subsystem.