From owner-freebsd-hackers@freebsd.org Mon Jun 3 22:27:41 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 214A515BFC15 for ; Mon, 3 Jun 2019 22:27:41 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf1-f66.google.com (mail-lf1-f66.google.com [209.85.167.66]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 987DF725B5 for ; Mon, 3 Jun 2019 22:27:40 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf1-f66.google.com with SMTP id b11so14858461lfa.5 for ; Mon, 03 Jun 2019 15:27:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XggKS49A9PzMPZlTBK+V8JGgLLkF9aJENCw5HGZlMAg=; b=gzgkdAU9rGel1CID2/Bof6V4Hj6pO3cKScIggptresDvC/eDMYbqgIc5/GdK9CUTUl NSxYqpYU60UOvPA/INGPoQ2mUl2QZ+mnxLDnmuUt4ODNGOclZP/xy194kUFSvrwmM/09 ic9IHX8i1w+xMQBXxTdu8K2nYPq93v4Vp8hZfPTH3U7e5Y8AHFwHHNez2lk9+b7l2oQd H3H5n1J93mMf+S/TUu5uDvQgfEaZrIPRr2IsnVrEqAo60E7rqsIN6BykAbr2pDsIL1vH DupIP8lDc8qbvBgqB5MbogoZ2euP2fiCoi6cmOv5Ctc62xWRruex+DQtL7BmHZQ3c4xX H21g== X-Gm-Message-State: APjAAAV14tRS2mphmt8CyxoMw2k0uIVDhXNsVdNFS96G4A9b3emUf733 xml1eedQl5+lHFD4M44APLe5vtnNExF0zjT+fRw= X-Google-Smtp-Source: APXvYqxyk11ExcFiSNqL4fGZNPtZ2ox62qKcptUnD1Euo602feiiqGnuFl9qdNlqanfiZE6ce3Pl+2St3SYZ5NDT/8A= X-Received: by 2002:ac2:4202:: with SMTP id y2mr8585375lfh.178.1559600857982; Mon, 03 Jun 2019 15:27:37 -0700 (PDT) MIME-Version: 1.0 References: <20190603211533.GS75280@kib.kiev.ua> In-Reply-To: <20190603211533.GS75280@kib.kiev.ua> From: Alan Somers Date: Mon, 3 Jun 2019 16:27:26 -0600 Message-ID: Subject: Re: How to VOP_RECLAIM on demand? To: Konstantin Belousov Cc: FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 987DF725B5 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.992,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jun 2019 22:27:41 -0000 On Mon, Jun 3, 2019 at 3:15 PM Konstantin Belousov wrote: > > On Mon, Jun 03, 2019 at 02:38:11PM -0600, Alan Somers wrote: > > It would be useful if I could trigger VOP_RECLAIM on demand for a > > certain file or pathname. There are some edge cases in fusefs that I > > can't test otherwise. But I don't see any way to do it. Is such a > > thing possible? Would it be worth adding a special syscall for this > > purpose? It could be guarded with INVARIANTS so it wouldn't affect > > production builds. > > Look at revoke(2) and VOP_REVOKE(). It is only implemented and used > for devfs tty nodes. I don't understand how that would help. What does VOP_REVOKE have in common with VOP_RECLAIM?