From owner-freebsd-fs@freebsd.org Fri Aug 11 22:17:25 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 6F93EDCAF45 for ; Fri, 11 Aug 2017 22:17:25 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-pf0-f180.google.com (mail-pf0-f180.google.com [209.85.192.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ABE96703A for ; Fri, 11 Aug 2017 22:17:25 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-pf0-f180.google.com with SMTP id t86so20714757pfe.2 for ; Fri, 11 Aug 2017 15:17:25 -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:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=xcbqJ/szMcGiPbrAKymAPrTVRtdeikCyMWPWYwZHmsw=; b=cnJAtT5D6uGbmX1zmhKKmeGzciRKqCw5xvoRkean0KEMVMtnrB96Zf5OgsfZeoHAA+ chr1GpJSylUiBaIIYLX7iJXTO3QN9JkcVj5YXBmT/JsqoDzZYEPoQ2Er1w9Guw9sZYdh 342IWGFyQAiiIbZ2mB9Ai0/n3acmXwLdLVPUQVD0Z2wpoDpVeeFk7qRFfnVif9GTm3LJ 8vAhYC3d0rk2Ma25vcu9h5ANBcoe1TfqAbUIWvykFpullccjEICAiTMLAO0xaWLl56sT rJf9moM2eUG4cppunDsNPbnzQvFoggdatqkbrFLShin5GYwqu63SkZWvTjSijW4bn2RT 8BfA== X-Gm-Message-State: AHYfb5iq7qqxUsD6VmS3vcPm6jJLLdiCIKyd5UKpGXMWfb+BcoT2qFHG bXMnkgKjIDaNW3A/Zss= X-Received: by 10.99.109.66 with SMTP id i63mr4199292pgc.187.1502483553203; Fri, 11 Aug 2017 13:32:33 -0700 (PDT) Received: from mail-pg0-f54.google.com (mail-pg0-f54.google.com. [74.125.83.54]) by smtp.gmail.com with ESMTPSA id w8sm5572594pgc.1.2017.08.11.13.32.32 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Aug 2017 13:32:32 -0700 (PDT) Received: by mail-pg0-f54.google.com with SMTP id y129so19538203pgy.4 for ; Fri, 11 Aug 2017 13:32:32 -0700 (PDT) X-Received: by 10.101.90.7 with SMTP id y7mr16181502pgs.29.1502483552034; Fri, 11 Aug 2017 13:32:32 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.100.150.15 with HTTP; Fri, 11 Aug 2017 13:32:31 -0700 (PDT) In-Reply-To: <8760dudj9c.fsf@vostro.rath.org> References: <878tiqdjtc.fsf@vostro.rath.org> <8760dudj9c.fsf@vostro.rath.org> From: Conrad Meyer Date: Fri, 11 Aug 2017 13:32:31 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Status of FUSE in FreeBSD kernel To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" 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 22:17:25 -0000 Hi Nikolaus, These questions are probably best answered by reading the source. I grepped the FreeBSD tree for FUSE_NOTIFY_INVAL_INODE and did not see it. Looking around, I don't think we have any of the libfuse notify support. As far as mknod/mkfifo, that should work. EINVAL can come from bogus dev value for a CHR/BLK mknod or an unrecognized mode type. Best, Conrad On Fri, Aug 11, 2017 at 11:58 AM, Nikolaus Rath wrote: > On Aug 11 2017, Nikolaus Rath wrote: >> 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