From owner-freebsd-fs@freebsd.org Fri Aug 11 18:58:11 2017 Return-Path: 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 33792D93EE9 for ; Fri, 11 Aug 2017 18:58:11 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 063BB8346E for ; Fri, 11 Aug 2017 18:58:10 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D700F20D7A for ; Fri, 11 Aug 2017 14:58:09 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 14:58:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=slQmnrGrQsRn6OJUuhoTVNzkYr9QE3n6a8aQVn1h3eI=; b=eJdHTK1G p0Agp/L8/VOTMf7fSqJrXTTQF2y2CC6sM8PRF3Ws8Oa2MFXXld6+joKAwu5o6cn/ R1GEqI5TwVRKf2XiYylTQQ+Scg64h2VGBAGP39QBl1mEf57LqKhvsuHLPzprIpfM Q/Beiscx/FoZaRW6Xxynaev4K5etsMtRgqqNIr+MPtNWt4mGGkbwdY2acDRuHBkF FzHr25imIcSqjiWyhFfWALEcX2VIAv4zD1xH6YLDeQIOtjaJDijGtBxPaKzfaqpc cFPp6TDtI9pc07mNny+i+OrRJgtfwuZ16sft3WnecLEWzSBQMKIyDT/BwAEvjgHm pHAhuzQA3CfBeQ== X-ME-Sender: X-Sasl-enc: MF6wgt6aW1wPT+76o5dnLeTa9L2aXO8AX6R5oDRsS/wT 1502477889 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 965B524442 for ; Fri, 11 Aug 2017 14:58:09 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id BCC90D9 for ; Fri, 11 Aug 2017 18:58:08 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 44CBA102E4A; Fri, 11 Aug 2017 20:58:07 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: Status of FUSE in FreeBSD kernel References: <878tiqdjtc.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 20:58:07 +0200 In-Reply-To: <878tiqdjtc.fsf@vostro.rath.org> (Nikolaus Rath's message of "Fri, 11 Aug 2017 20:46:07 +0200") Message-ID: <8760dudj9c.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 18:58:11 -0000 On Aug 11 2017, 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. Another example: calling 'mknod' or 'mkfifo' on a FUSE mountpoint doesn't seem to make it through to the filesystem, the kernel returns -EINVAL instead. Is that a problem with the filesystem, or not supported by the kernel? Thanks! -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB