From owner-freebsd-current@FreeBSD.ORG Fri Mar 9 18:31:08 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E035106564A; Fri, 9 Mar 2012 18:31:08 +0000 (UTC) (envelope-from gnn@freebsd.org) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) by mx1.freebsd.org (Postfix) with ESMTP id 705CB8FC14; Fri, 9 Mar 2012 18:31:08 +0000 (UTC) Received: from [209.249.190.124] (helo=[10.2.212.229]) by vps.hungerhost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1S64ap-0007OW-V2; Fri, 09 Mar 2012 13:31:07 -0500 Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: George Neville-Neil In-Reply-To: <20120308225407.GV75778@deviant.kiev.zoral.com.ua> Date: Fri, 9 Mar 2012 13:31:14 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <8CDE3851-6C32-41ED-8CD0-70EC1BA245C5@freebsd.org> References: <20120308225407.GV75778@deviant.kiev.zoral.com.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.1257) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - freebsd.org Cc: current@freebsd.org, fs@freebsd.org Subject: Re: RFC: FUSE kernel module for the kernel... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2012 18:31:08 -0000 On Mar 8, 2012, at 17:54 , Konstantin Belousov wrote: > I just took a very quick look, and the code has all usual bugs. E.g., = the > filesystem is marked mpsafe, while insmntque() is performed before new > vnode is initialized. >=20 > The fuse was known to cause random kernel memory corruption, were the = issues > identified and fixed ? >=20 They are being identified and fixed as we speak. I fixed a couple = yesterday. > Who is going to maintain the code ? I once objected strongly for = throwing > the fuse into svn without first fixing bugs, and having a maintainer. I'm planning to maintain the code. As bugs arise I will take care of = them. I've been using fsx to seek them out. Best, George