From owner-freebsd-fs@freebsd.org  Mon Aug 14 06:14:59 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E94FDD78D3
 for <freebsd-fs@mailman.ysv.freebsd.org>; Mon, 14 Aug 2017 06:14:59 +0000 (UTC)
 (envelope-from lars@e-new.0x20.net)
Received: from mail.0x20.net (mail.0x20.net [46.251.251.56])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "0x20.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 156316F378;
 Mon, 14 Aug 2017 06:14:58 +0000 (UTC)
 (envelope-from lars@e-new.0x20.net)
Received: from e-new.0x20.net (e-new.0x20.net [217.69.76.210])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.0x20.net (Postfix) with ESMTPS id 2B5CD8DA7B;
 Mon, 14 Aug 2017 08:04:49 +0200 (CEST)
Received: from e-new.0x20.net (localhost [127.0.0.1])
 by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id v7E64uMu028551;
 Mon, 14 Aug 2017 08:04:56 +0200 (CEST)
 (envelope-from lars@e-new.0x20.net)
Received: (from lars@localhost)
 by e-new.0x20.net (8.14.7/8.14.7/Submit) id v7E64uAI028255;
 Mon, 14 Aug 2017 08:04:56 +0200 (CEST) (envelope-from lars)
Date: Mon, 14 Aug 2017 08:04:56 +0200
From: Lars Engels <lars.engels@0x20.net>
To: freebsd-fs@freebsd.org
Cc: gnn@FreeBSD.org
Subject: Re: Status of FUSE in FreeBSD kernel
Message-ID: <20170814060456.GE48929@e-new.0x20.net>
References: <878tiqdjtc.fsf@vostro.rath.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <878tiqdjtc.fsf@vostro.rath.org>
X-Editor: VIM - Vi IMproved 7.4
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Aug 2017 06:14:59 -0000

On Fri, Aug 11, 2017 at 08:46:07PM +0200, Nikolaus Rath wrote:
> Hello,
> 
> Is there some resource that gives an overview of the features supported
> by the FUSE kernel module in FreeBSD?
> 
> For example, I am wondering if the EINVAL error that I'm getting when
> sending FUSE_NOTIFY_INVAL_INODE requests to FUSE is because of an error
> on my side, or because the FreeBSD kernel just doesn't support it.
> 
> I expect to encounter the same question for a number of other functions,
> e.g. the other FUSE_NOTIFY_* requests.
> 
> Thanks,
> -Nikolaus

George Neville-Neil (CC'ed) wrote FreeBSD's fuse kernel module. Maybe he
can help you.


-- 

Lars