Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1531115ybi; Sat, 25 May 2019 04:12:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqzgyXe66ghImAa9sOnIclHKSPP0BRRemT/yn1MpN1CsCkgT1Kf8tqxJ8vGBGuYw66xi0EqS X-Received: by 2002:a17:902:e28a:: with SMTP id cf10mr109378186plb.77.1558782747991; Sat, 25 May 2019 04:12:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558782747; cv=none; d=google.com; s=arc-20160816; b=TklobehsdtgPSgiwBrMLlKUw8ZTENAIcL7Ez8WLn1rU3IDn4BZ+/au1chwIL+rZGOt zUFUmnRuqgMmCadLPSoeKEgmQpYK/trb2+Ms2f1nUkSd52CVGsHZxVI/OIf2IMmcQuRd 8qw6SJnC3DPnYV1tXIoEnkhY4u9mJ2u93R74Df/J9VYFt5nFDe1Z/kPlFU+FgiBdLZpf x25+TcT5OztuZdhyr1M0VdTpR6CSHc0DwCdAUwcDWQlnrCmAJjnz5hHa1h6Fb34/B0+x BEN5BD8rnLidYjwdEREEDrNk9/UPw9po1YWHQyZlk1oAHuiNVR09xEt7TM2/5BE40Lmd KoXw== 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=s7tfElOush7WmpXwDt5KtoG/QxJ8ZhZFKtM952iazT4=; b=0qmykVsjXwVPb/6QQY0tA+0MWN084DtMX3e5B82OumQ1nFTNuv+SC/Uv1Wq0umeszO sypjmgSElR/1lVp+fYbEsIE/D0FgEYGcdB05hO/kVVPUMhc0OlsChoLMP+zpzdytOJ5D ij3U3k3V3nn90/d6p4fnH4vMbIfy3GDR3R9hmMEdbHByAOPskdkd40IoTMn2dpdirKZ/ BhQz9xvZig20263QZkjUxDo11kpGhb9V3J2bhRtWHorFDg/qTn3uzAgbIYoqXLEtsPab dtDJWwCu1FkQ/42pcHdI+kGq3AzXHnEuOK2R5KEWAYevqZkU6bKnvVI/dInxi9aBLsrd G45A== 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 n24si5808015pgk.200.2019.05.25.04.11.56; Sat, 25 May 2019 04:12:27 -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 S1726833AbfEYLJR (ORCPT + 99 others); Sat, 25 May 2019 07:09:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59272 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726484AbfEYLJR (ORCPT ); Sat, 25 May 2019 07:09:17 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 3503B37EEA; Sat, 25 May 2019 11:09:17 +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 A646060FAD; Sat, 25 May 2019 11:09:16 +0000 (UTC) From: "Benjamin Coddington" To: "J. Bruce Fields" Cc: "J . Bruce Fields" , jlayton@kernel.org, linux-nfs@vger.kernel.org Subject: Re: [PATCH v2 0/5] NLM fl_pid fixup Date: Sat, 25 May 2019 07:09:17 -0400 Message-ID: <114775E1-D195-4DE1-8920-CC750DBB44C2@redhat.com> In-Reply-To: <20190524164759.GA23881@fieldses.org> References: <20190524164759.GA23881@fieldses.org> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Sat, 25 May 2019 11:09:17 +0000 (UTC) Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On 24 May 2019, at 12:47, J. Bruce Fields wrote: > On Thu, May 23, 2019 at 10:45:43AM -0400, Benjamin Coddington wrote: >> This series aims to correct the fl_pid value for locks held by the >> NLM >> server, or lockd. It applies onto the revert of the previous attempt >> to fix >> this problem sent ealier this week: '[PATCH] Revert "lockd: Show pid >> of >> lockd for remote locks"'. >> >> The problem with the earlier attempt was that we discarded the svid, >> and so >> we couldn't distinguish remote lockowners on each host. It is >> necessary to >> turn the svid and host into a distinct owner. > > So, to make sure I understand, we've got multiple ways to identify a > lock owner: > > - the svid, the pid of the client process: this gets returned to > the client in grant callbacks and (possibly to a different > client) in testd results. > - the pid of the server's lockd process: this is what other > processes on the server see as the owner of locks held by nfs > clients. > - the nlm_lockowner: a (nlm_host, svid) pair, used to actually > decide when locks conflict. That's it. > Makes sense to me. > > I'll send your earlier revert to stable, then add this on top for the > 5.3 merge window. Sound OK? Sounds great, thank you! Ben