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_SANE_1 autolearn=no 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 BB0A3C3A5A0 for ; Wed, 21 Aug 2019 23:49:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9091222CE3 for ; Wed, 21 Aug 2019 23:49:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="gPyjbbOl" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730832AbfHUXts (ORCPT ); Wed, 21 Aug 2019 19:49:48 -0400 Received: from mail-qt1-f194.google.com ([209.85.160.194]:43539 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729486AbfHUXtr (ORCPT ); Wed, 21 Aug 2019 19:49:47 -0400 Received: by mail-qt1-f194.google.com with SMTP id b11so5313355qtp.10 for ; Wed, 21 Aug 2019 16:49:47 -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=8Dz6lpgjK94wsk5MHL4jboQE1NnpsCOBFBvUAahO07A=; b=gPyjbbOlWbFMNLNEHlm3dVB7Uzz3AKtizx4gilO4AsJS5UDSi7tKtuKLliMJh4+rPu 1Jf/sMigbAhn4QGVmiCQ6jvV0hXBmnUimeqP0xUMpcAFxLHy5mSvYZ2fitBb6fMv1QEd cZ2rJhYAzO91SSmOVmphbBBxbh+HSxrYlvJ3tgnRnP1JDEhZkz5GiMo9UEiNo9GyVRUF 8WnH6kAl7p/wnpPhgEWF5q/2JAvm1wPyF94nsUIZ3Nn/qacJn/LeA6n513wpAcQCJroq gRk02pguSic3ESpZjlGMGpJT0L4SvQqRx3eSvDn9QgwMdBegopEE9vJkJ6UvTjj8CtPC e/+g== 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=8Dz6lpgjK94wsk5MHL4jboQE1NnpsCOBFBvUAahO07A=; b=RuvoG+QMgXti+bqyczCbAMHT+0H96IhvRqzZV2wivdCb1JIf1AHQRriK1AuC3ZkqBz 8KLXsoVqzXiewqoa3ZqIQJFcwVy+CqzhueDIygvGg2ueT+6IAy8swJRJYYGq7i/H98xK S1YI/29NHlu7/RY/uESSoBlLZfVOoNKojC7JInjum4z1f3qiILDKvifqEoSSM/FvQgOz MDvM4zfxN6shi6hpcKUFm205aIHs71WC0WQT3bRwBx3niwksxtmm4yGcFsjsrT7KRn0v NKwr3xaABkeVUDBA0pg/6m5VmgtkF+0TOY98jfmcCJwlcZUSMz1UnR6753zX/eHAQdAg Xuyw== X-Gm-Message-State: APjAAAWo0GmYPpiMtMxYjd/hJEA1qPQM8BuJOVYk0FBrZA9pL6/Fm2jT XsWQbk/uNvAsAbD8rICUdlHzVw== X-Google-Smtp-Source: APXvYqydXtesxNmJNprP51Mg7fYbplLAQObHr5i5Uy4KKN0cJaAIkir0EBD/uw5rTQeKc1g+BuOcEQ== X-Received: by 2002:ac8:22ac:: with SMTP id f41mr33955957qta.362.1566431386704; Wed, 21 Aug 2019 16:49:46 -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 125sm11156870qkl.36.2019.08.21.16.49.46 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 21 Aug 2019 16:49:46 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1i0aML-0008RC-Ks; Wed, 21 Aug 2019 20:49:45 -0300 Date: Wed, 21 Aug 2019 20:49:45 -0300 From: Jason Gunthorpe To: Ira Weiny Cc: Dave Chinner , Jan Kara , Andrew Morton , Dan Williams , Matthew Wilcox , Theodore Ts'o , John Hubbard , Michal Hocko , linux-xfs@vger.kernel.org, linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-nvdimm@lists.01.org, linux-ext4@vger.kernel.org, linux-mm@kvack.org Subject: Re: [RFC PATCH v2 00/19] RDMA/FS DAX truncate proposal V1,000,002 ;-) Message-ID: <20190821234945.GA31944@ziepe.ca> References: <20190819063412.GA20455@quack2.suse.cz> <20190819092409.GM7777@dread.disaster.area> <20190819123841.GC5058@ziepe.ca> <20190820011210.GP7777@dread.disaster.area> <20190820115515.GA29246@ziepe.ca> <20190821180200.GA5965@iweiny-DESK2.sc.intel.com> <20190821181343.GH8653@ziepe.ca> <20190821185703.GB5965@iweiny-DESK2.sc.intel.com> <20190821194810.GI8653@ziepe.ca> <20190821204421.GE5965@iweiny-DESK2.sc.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190821204421.GE5965@iweiny-DESK2.sc.intel.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Wed, Aug 21, 2019 at 01:44:21PM -0700, Ira Weiny wrote: > > The order FD's are closed during sigkill is not deterministic, so when > > all the fputs happen during a kill'd exit we could end up blocking in > > close(fd) as close(uverbs) will come after in the close > > list. close(uverbs) is the thing that does the dereg_mr and releases > > the pin. > > Of course, that is a different scenario which needs to be fixed in my patch > set. Now that my servers are back up I can hopefully make progress. (Power > was down for them yesterday). It isn't really a different scenario, the problem is that the filesystem fd must be closable independenly of fencing the MR to avoid deadlock cycles. Once you resolve that the issue of the uverbs FD out living it won't matter one bit if it is in the same process or another. Jason