From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E1A8CC31E49 for ; Thu, 13 Jun 2019 17:18:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B842C21473 for ; Thu, 13 Jun 2019 17:18:37 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="lpafWUUx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728216AbfFMRSg (ORCPT ); Thu, 13 Jun 2019 13:18:36 -0400 Received: from mail-qt1-f194.google.com ([209.85.160.194]:43547 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726835AbfFMRSg (ORCPT ); Thu, 13 Jun 2019 13:18:36 -0400 Received: by mail-qt1-f194.google.com with SMTP id z24so10220172qtj.10 for ; Thu, 13 Jun 2019 10:18:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ECRuDs1AAJXccME5fjhnIagUHhl7wP1zzfkz6zfy+gs=; b=lpafWUUxvoz6cw8t6bvxhkbpKx1MuDJC/6+rsfIk9kELesUHNICDeurjA/f9ZuoaJv lKvrldgcxc6rNvpGlf+9lPT2riW0RE1+HuS2OqxKuK9J/UHHXstRF22tdIYHVfy+KlvT LRXs02nEuzM/Fk4kx+1bbgAFr8bE6dMuPmxEyYZicAywAmS5YuFqquENcwoxV3ALaTJr wrm1jUeHUGOSNU/aAA8xVX35TgozP9YEYH5RVAbReFiyARjThtZ1Rs+sS5w3QP1kXXnb Bg53NxX8LuVo7QxF8lvDT58SoxeM97wjJy7wRjhtAvG+RnkgIyeQxLZquacOghksiJH/ /FWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ECRuDs1AAJXccME5fjhnIagUHhl7wP1zzfkz6zfy+gs=; b=oa2RkCdrEoYiJDCo+7BiY4eig5KqwJupoeEXfD2Jyd4NHb7MGPqD32WWDRgXDxAVyd r++r1tm2N8uNUHXBMgTPMlDoXS/ISC8bZy1ebBbJMTdym36z9t3NxkZqH5KHCZ64ZRi0 6yr5DitBR5jcBMc9A7sdrWW0Dez0xRXF+dAnMU74DFugVY6xDkYfl8USxDb0X1zLxPuC 0rB8GwaHD9AxhtOyGCgmi801QIe6dQaypkQAazsl0qzBUd3gutbyrF3mhC2xE+hW7ZmJ 3d8VTU3/nxDyTznmleLRc8988wS9fnZRbZ39dV3MDEMKoCFMq3vapb4RbPTuifwjnBEb oiWA== X-Gm-Message-State: APjAAAXa5ktR/fGvFVugDwy4JWXCAXhKhw+d8uONl2fABU7+vIK/fWGZ exs/O4jUFO8zv5l6c8i3gCxMMQ== X-Google-Smtp-Source: APXvYqxo9wZDsL+u9xxF1oR9luzN2plR83tNtwXpM5LjZTCeK+hD6TjhoexGVCwTWwyvS0UUHoLRyg== X-Received: by 2002:aed:3686:: with SMTP id f6mr53799960qtb.30.1560446315300; Thu, 13 Jun 2019 10:18:35 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-156-34-55-100.dhcp-dynamic.fibreop.ns.bellaliant.net. [156.34.55.100]) by smtp.gmail.com with ESMTPSA id l3sm76969qkd.49.2019.06.13.10.18.34 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 13 Jun 2019 10:18:34 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1hbTMw-000325-3P; Thu, 13 Jun 2019 14:18:34 -0300 Date: Thu, 13 Jun 2019 14:18:34 -0300 From: Jason Gunthorpe To: Dan Williams Cc: Ira Weiny , Jan Kara , Theodore Ts'o , Jeff Layton , Dave Chinner , Matthew Wilcox , linux-xfs , Andrew Morton , John Hubbard , =?utf-8?B?SsOpcsO0bWU=?= Glisse , linux-fsdevel , Linux Kernel Mailing List , linux-nvdimm , linux-ext4 , Linux MM Subject: Re: [PATCH RFC 00/10] RDMA/FS DAX truncate proposal Message-ID: <20190613171834.GE22901@ziepe.ca> References: <20190612102917.GB14578@quack2.suse.cz> <20190612114721.GB3876@ziepe.ca> <20190612120907.GC14578@quack2.suse.cz> <20190612191421.GM3876@ziepe.ca> <20190612221336.GA27080@iweiny-DESK2.sc.intel.com> <20190612233324.GE14336@iweiny-DESK2.sc.intel.com> <20190613151354.GC22901@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 13, 2019 at 09:25:54AM -0700, Dan Williams wrote: > On Thu, Jun 13, 2019 at 8:14 AM Jason Gunthorpe wrote: > > > > On Wed, Jun 12, 2019 at 06:14:46PM -0700, Dan Williams wrote: > > > > Effectively, we would need a way for an admin to close a specific file > > > > descriptor (or set of fds) which point to that file. AFAIK there is no way to > > > > do that at all, is there? > > > > > > Even if there were that gets back to my other question, does RDMA > > > teardown happen at close(fd), or at final fput() of the 'struct > > > file'? > > > > AFAIK there is no kernel side driver hook for close(fd). > > > > rdma uses a normal chardev so it's lifetime is linked to the file_ops > > release, which is called on last fput. So all the mmaps, all the dups, > > everything must go before it releases its resources. > > Oh, I must have missed where this conversation started talking about > the driver-device fd. In the first paragraph above where Ira is musing about 'close a specific file', he is talking about the driver-device fd. Ie unilaterally closing /dev/uverbs as a punishment for an application that used leases wrong: ie that released its lease with the RDMA is still ongoing. Jason