Date: Mon, 23 Aug 2010 16:57:40 +0200 From: Ian FREISLICH <ianf@clue.co.za> Cc: Kostik Belousov <kostikbel@gmail.com>, Ed Schouten <ed@80386.nl>, freebsd-current@freebsd.org Subject: Re: fusefs-kmod broken? Message-ID: <E1OnYSy-0001e9-Vv@clue.co.za> In-Reply-To: <E1OnY55-0001YZ-0L@clue.co.za> References: <E1OnY55-0001YZ-0L@clue.co.za> <20100823140149.GG2396@deviant.kiev.zoral.com.ua> <201008230826.49509.jhb@freebsd.org> <E1OmUBI-0000Oy-J5@clue.co.za> <E1OnWc7-0001Kv-47@clue.co.za> <20100823132551.GE2396@deviant.kiev.zoral.com.ua> <20100823133555.GA64651@hoeg.nl> <20100823134459.GF2396@deviant.kiev.zoral.com.ua> <20100823134723.GC64651@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian FREISLICH wrote:
> So, in this case is the fusefs module broken? I'm guessing it is.
> I don't like the way fuse_fileops is initialised in fuse4bsd. I
> would prefer for the struct to be zeroed and then the fo_xxx
> implimented bits set as appropriate. That way when the struct is
> changed, you don't get stung again.
I am an idiot - that will have no effect. This patch needs to be
included in sysutils/fusefs-kmod/files
--
Ian Freislich
patch-fuse_module__fuse_main.c
--- fuse_module/fuse_main.c.orig 2010-08-23 16:52:20.000000000 +0200
+++ fuse_module/fuse_main.c 2010-08-23 16:48:17.000000000 +0200
@@ -108,6 +108,7 @@
switch (what) {
case MOD_LOAD: /* kldload */
+ fuse_fileops.fo_truncate = vnops.fo_truncate;
fuse_fileops.fo_ioctl = vnops.fo_ioctl;
fuse_fileops.fo_poll = vnops.fo_poll;
fuse_fileops.fo_kqfilter = vnops.fo_kqfilter;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1OnYSy-0001e9-Vv>