Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp3425275pxb; Thu, 10 Feb 2022 22:14:26 -0800 (PST) X-Google-Smtp-Source: ABdhPJz6GqT3r0BhElJmP9EyGdbPqRmO09OV9GxUTC0p7qIiOIr5ZvKDzGHLfTjBlfkWdZhN1U8L X-Received: by 2002:a17:90b:1e05:: with SMTP id pg5mr1142514pjb.86.1644560065888; Thu, 10 Feb 2022 22:14:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644560065; cv=none; d=google.com; s=arc-20160816; b=uDX4qW6sSFlAwHaih2e08+1NvWkbXqX/Lf3+SnJ41AL1nxw+VAxpOM4ILAOtsh/gK7 zVhwMpjBYBsVYFsW0mQNTOvbPubIinG8mU0AmMJB+JJ7RqeDVjjf6ZyheVqdKbrU4ayF Eotdq5cJFnolJAxf/KJLPPY/xvUCBguuPvGRxOvN75Yb7BQeztgq9IpTU3BZUFIpQgux /0BdVV9ovy7WxJ2m7HsVTPlrWRTDAVAukD/w139RAB8ohDHEduxx8wlj23E54h1Tr5sK LGfFyWnV8OuIwSUts/XaBfd25DYen10Gi9MwFS1ExmfU8Lvkdcw8vnmd2gd/nPng4wT9 +Kew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature:dkim-filter; bh=bJ6y98wbmIYdcbJEh9WTmMjbBupTCJb/ugof+qHQeYs=; b=fPH4zHvHO3Hd8y8yLRHjSoPgbf6sYwD2E5SVDEASRPo4d/0YpzY/4vP+O7obuKn2+n Xe2qCaBGp6PJDgdl311wVLic2yUdRQyqLYASuxDlLoKlbb9f4ZA2oZhuIC8+QEqU91Sf VS5BUEq+KDL8s9jcwgaHtvk3cK6dESCGrTMgkpwBjbj/BygAHcgdWCZY5Db0zHE8U0xQ MgMqZzNxsPbiOASBB4e4skVbZc7k8cRsezo2MxDjm6d5S8eb3nRLMf2Q/WkoNRLCHqcF xraGLKob0NR1bDtOV3bw/cQwayXJ2MH/FLa/uhcVc8mP8fzcAD01L/SKnEzRC8IHoJKz WRSQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@fieldses.org header.s=default header.b=Pvr2bqXs; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z7si3325286plk.369.2022.02.10.22.14.03; Thu, 10 Feb 2022 22:14:25 -0800 (PST) Received-SPF: pass (google.com: domain of linux-nfs-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=@fieldses.org header.s=default header.b=Pvr2bqXs; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242920AbiBJO2Z (ORCPT + 99 others); Thu, 10 Feb 2022 09:28:25 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:44120 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242924AbiBJO2Z (ORCPT ); Thu, 10 Feb 2022 09:28:25 -0500 Received: from fieldses.org (fieldses.org [IPv6:2600:3c00:e000:2f7::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DA53FB19; Thu, 10 Feb 2022 06:28:26 -0800 (PST) Received: by fieldses.org (Postfix, from userid 2815) id 6086EBDE; Thu, 10 Feb 2022 09:28:26 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.11.0 fieldses.org 6086EBDE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fieldses.org; s=default; t=1644503306; bh=bJ6y98wbmIYdcbJEh9WTmMjbBupTCJb/ugof+qHQeYs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Pvr2bqXsVIE6dmDphzBIHsyJT9iXJmri4j4iHpyA//NZ8YRHnjiSOkNRn68o9skoD PNEtbLt/yYZ3UoFXMBvheQyMMYIZlRKlbAThOY+T9j6zMRMC2vBeL3MlLQZaT2h17r /RWwaYuCwjs5NG+kj6Lxx0twbQb95HDynOffYGCg= Date: Thu, 10 Feb 2022 09:28:26 -0500 From: "J. Bruce Fields" To: Dai Ngo Cc: chuck.lever@oracle.com, jlayton@redhat.com, viro@zeniv.linux.org.uk, linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH RFC v12 1/3] fs/lock: add new callback, lm_lock_conflict, to lock_manager_operations Message-ID: <20220210142826.GD21434@fieldses.org> References: <1644468729-30383-1-git-send-email-dai.ngo@oracle.com> <1644468729-30383-2-git-send-email-dai.ngo@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1644468729-30383-2-git-send-email-dai.ngo@oracle.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE 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-nfs@vger.kernel.org On Wed, Feb 09, 2022 at 08:52:07PM -0800, Dai Ngo wrote: > diff --git a/include/linux/fs.h b/include/linux/fs.h > index bbf812ce89a8..726d0005e32f 100644 > --- a/include/linux/fs.h > +++ b/include/linux/fs.h > @@ -1068,6 +1068,14 @@ struct lock_manager_operations { > int (*lm_change)(struct file_lock *, int, struct list_head *); > void (*lm_setup)(struct file_lock *, void **); > bool (*lm_breaker_owns_lease)(struct file_lock *); > + /* > + * This callback function is called after a lock conflict is > + * detected. This allows the lock manager of the lock that > + * causes the conflict to see if the conflict can be resolved > + * somehow. If it can then this callback returns false; the > + * conflict was resolved, else returns true. > + */ > + bool (*lm_lock_conflict)(struct file_lock *cfl); > }; I don't love that name. The function isn't checking for a lock conflict--it'd have to know *what* the lock is conflicting with. It's being told whether the lock is still valid. I'd prefer lm_lock_expired(), with the opposite return values. (Apologies if this has already been woodshedded to death, I haven't been following.) --b.