Received: by 2002:a25:86ce:0:0:0:0:0 with SMTP id y14csp826341ybm; Tue, 21 May 2019 04:19:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqyH2fMtoyfIsrXg2ikzAvVeEtbX7yGWxLs2cjNzhj/mqO9xk5hpRWpBka6PrnuJ5THGIHhS X-Received: by 2002:a17:902:9f85:: with SMTP id g5mr76765797plq.29.1558437574405; Tue, 21 May 2019 04:19:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558437574; cv=none; d=google.com; s=arc-20160816; b=B5+mRo8pWcxO0KDoASaOqPFeIvXbcXxj6a6hxA4u88Y49fd76oXzmmkxnmHoH18Qym aFxDw2QnPT+272zolL2RAU9rYjN6j4WgKL+hbZAJit2s5CrtHmA37gHBM1Cc8YnU1jXW 94qKeJ3eKVkOdHqDN9QJodMFMLXRtqCpSnzHw+Wg+wo4UMI5s6cMmdEwR9ivmOuQ4Iev 6rjGSmawCY+dlbMEIVKOo7GFEuqgh9nF8MLxPZ0qYP0ZsD8VqmUVn3FHPCa/kman4c0U yCA781TiBy+0RBendSWuFt4o4Ry1xHSdC+W2r94OJzZeacVM1V2HSrPEHYfRFUPMqNpF wyxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=76yNxRRtdSRXhGnup1RKjZKJFMB8jDhOJqNX7OJVM3o=; b=zAUooOuNx40z+MrjvxL7TkY9SZdaI+U9N6tPy4sw16/ebnXZgHP2hkHvsp/9DsDZKx ON0K/b4pg4Yn1VaefjuPGbWavdZqWeer6S0b/vXEpq4XhEC5eAF5+BYquleDHtqYiEYJ dwF+tnQbmzAfcoN/s5FftlR/szAuU5DCT32HB34rjqv69lVV3ekwRzywcU7sOaVSgkd7 LfzZCnMvjGfUfTt1+EZlEhyTVxGam3o0vS12ZtCIkXoUTNNettRII7CO4M8I4G2p86u2 f5wgLzgZJ/kUU1PiymOe5r70OYj58hFfnTMmCNGZtPmXj2sWCoGbOs20SRz3rcdwXdXV 9dcg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y184si19415341pgd.546.2019.05.21.04.19.07; Tue, 21 May 2019 04:19:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726525AbfEULTF (ORCPT + 99 others); Tue, 21 May 2019 07:19:05 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57602 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726344AbfEULTF (ORCPT ); Tue, 21 May 2019 07:19:05 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 31A013082E6B; Tue, 21 May 2019 11:19:00 +0000 (UTC) Received: from [10.10.66.2] (ovpn-66-2.rdu2.redhat.com [10.10.66.2]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A3773665F4; Tue, 21 May 2019 11:18:57 +0000 (UTC) From: "Benjamin Coddington" To: "J. Bruce Fields" Cc: "Xuewei Zhang" , jlayton@kernel.org, "Grigor Avagyan" , "Trevor Bourget" , "Nauman Rafique" , trond.myklebust@hammerspace.com, anna.schumaker@netapp.com, linux-nfs@vger.kernel.org Subject: Re: [PATCH] lockd: Show pid of lockd for remote locks Date: Tue, 21 May 2019 07:18:57 -0400 Message-ID: In-Reply-To: <20190520205106.GA29025@fieldses.org> References: <3A924C3F-A161-4EE2-A74E-2EE1B6D2CA14@redhat.com> <20190520205106.GA29025@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Tue, 21 May 2019 11:19:05 +0000 (UTC) Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On 20 May 2019, at 16:51, J. Bruce Fields wrote: > On Mon, May 20, 2019 at 10:22:00AM -0400, Benjamin Coddington wrote: >> Ok, I just noticed that we set fl_owner to the nlm_host in >> nlm4svc_retrieve_args, so things are not as dire as I thought. What >> would be nice is a sane set of tests for NLM.. > > What would we have needed to catch this? Sounds like it turns > multi-client testing wouldn't have been required? (Not that that > would > be a bad idea.) Two NLM clients would be ideal to exercise the full range of expected lock behavior. I suspect that's something I can do with what's in pynfs today, but I haven't looked yet. I suppose if there's a test for NLM I should make one for v4 too.. Ben