Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp806935ybh; Tue, 21 Jul 2020 08:21:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyWLi2WV8rvlO8LJG21402ZTtbWaakbvogtWY+2Y1CNxBy6Ezox1nJQXvNrmD8f1NI2ZtQT X-Received: by 2002:a50:8adb:: with SMTP id k27mr25357171edk.267.1595344881981; Tue, 21 Jul 2020 08:21:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595344881; cv=none; d=google.com; s=arc-20160816; b=wku9jENiOdpBgD3rNbIejQiRdwMpCRYv1gYzPzmJ+BNaDRrdv7mKhzmstBtfYlBzWc pg7DgT/5BQwI6Q3pnW/ibfjnv2drqc+f2cZFwVwsWYfh2pBHoMQCj8wzdm8Hf67XJDiS Xlf427Y3B09jpVtspoeHFYay4p3k/v15R2OvULkd4PSILziiz9iaO2RwMYVceVynASO3 FlzueHNpr1X2D53V0RtwgjtZB8fCBrfmhr8l69/1IpjnQf2xjthb6KCn4KpYoIXX/Bco 4v1TuGuKBQOYZMtXeFhSyjuP6NVQA2iuG6DO2pT4NA5ArSAroMJBAjIharfosDogpf4U XdsA== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=iKuDsPoUOkgv4Eh9ysVNrnYJ3BM7sRpNuQi6UyjZAxs=; b=Nimg1WnwNeljIBh3PGkBALHUj0Lr2nQ8/a6PZTK8Yl+mqD730SyRz6JEkpzXd7qTxw RJSpMrb5xGRxg5ZhA/Xsrg6R0xgmkdevqZntlZHudYeJYKTxRqPcDe9HFOvfpoMFTXyg s3l9Yb3SPfl20aA3/bjkJKH9uR13jWtcTu8o4OgMvtNJ/CBeIkYzv7UNQFA/6MO+kYxz 1gp02WSqLkQJpO33Q1SDb2N2qjIKCwXJ0I4gcuJ7TBgX4kI7/03YrWMp77iMyHiUzxH6 VVexUnVIbHBIM8yvY0Y8NQPEnLNQcN7e3VSZN/yMGJANZLoh/038DLMhjhg0m5JCvbmQ TKnQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hru92H9m; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i4si13159889edr.244.2020.07.21.08.20.55; Tue, 21 Jul 2020 08:21:21 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=hru92H9m; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728755AbgGUPUi (ORCPT + 99 others); Tue, 21 Jul 2020 11:20:38 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:42181 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726654AbgGUPUi (ORCPT ); Tue, 21 Jul 2020 11:20:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1595344837; h=from:from:reply-to:subject:subject: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=iKuDsPoUOkgv4Eh9ysVNrnYJ3BM7sRpNuQi6UyjZAxs=; b=hru92H9m1s2blWbmMSVI25d9efw0jbet5LMTkCXb116nvgmaRJ6TLph+ngCOvdTO9t0tmh +66GsKTrfoxKIvPCZi8XRSgPnQgXkr/HsAfDfXdDvOE1xYKaFmcPgRwmt1W8kOL6IlbQbc kZYD8SunBc6ZjE69/C1QtoFwR+TPEDo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-329-chozkSUaPD2E-ZLmiJp-pg-1; Tue, 21 Jul 2020 11:20:33 -0400 X-MC-Unique: chozkSUaPD2E-ZLmiJp-pg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A125A10059A2; Tue, 21 Jul 2020 15:20:32 +0000 (UTC) Received: from madhat.boston.devel.redhat.com (ovpn-113-147.phx2.redhat.com [10.3.113.147]) by smtp.corp.redhat.com (Postfix) with ESMTP id 3333810002B5; Tue, 21 Jul 2020 15:20:32 +0000 (UTC) Subject: Re: [PATCH v2 4/4] nfs-utils: Update nfs4_unique_id module parameter from the nfs.conf value To: Chuck Lever Cc: Alice Mitchell , Linux NFS Mailing List References: <4dc8c372324d551456a47e60d73d926d96fc0d24.camel@redhat.com> From: Steve Dickson Message-ID: <8584c1f2-c771-8b07-7759-e597e3011544@RedHat.com> Date: Tue, 21 Jul 2020 11:20:31 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org Hey! On 7/20/20 2:23 PM, Chuck Lever wrote: > > >> On Jul 20, 2020, at 1:54 PM, Steve Dickson wrote: >> >> Hello, >> >> On 7/19/20 3:57 PM, Alice Mitchell wrote: >>> Hi Chuck, >>> I must have missed the discussion on Trond's work sorry, and I agree >>> that having it fixed in a way that is both automatic and transparent to >>> the user is far preferable to the solution I have posted. Do we have >>> any timeline on this yet ? >> I too did missed the discussion... Chuck or Trond can you give us more >> context on how this is going to work automatically and transparent? >> Is there a thread you can point us to? > > https://lore.kernel.org/linux-nfs/20190611180832.119488-1-trond.myklebust@hammerspace.com/ Thanks! That is the kernel support but you mentioned something about a udev-based mechanism for automation... What the story on that? steved.