From owner-freebsd-arch@FreeBSD.ORG Mon Oct 25 22:37:31 2010 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFE3F1065675 for ; Mon, 25 Oct 2010 22:37:31 +0000 (UTC) (envelope-from freebsd-arch@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 970BF8FC26 for ; Mon, 25 Oct 2010 22:37:31 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PAVfT-00044m-OH for freebsd-arch@freebsd.org; Tue, 26 Oct 2010 00:37:27 +0200 Received: from 78-1-180-0.adsl.net.t-com.hr ([78.1.180.0]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Oct 2010 00:37:27 +0200 Received: from ivoras by 78-1-180-0.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Oct 2010 00:37:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-arch@freebsd.org From: Ivan Voras Date: Tue, 26 Oct 2010 00:37:18 +0200 Lines: 30 Message-ID: References: <20101025211904.GM2392@deviant.kiev.zoral.com.ua> <20101025214630.GO2392@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-180-0.adsl.net.t-com.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.9) Gecko/20101008 Thunderbird/3.1.4 In-Reply-To: <20101025214630.GO2392@deviant.kiev.zoral.com.ua> Subject: Re: Importing the fusefs kernel module? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2010 22:37:32 -0000 On 10/25/10 23:46, Kostik Belousov wrote: > On Mon, Oct 25, 2010 at 11:38:44PM +0200, Ivan Voras wrote: >> On 10/25/10 23:19, Kostik Belousov wrote: >> >>> This is not going to work. The code is unmaintained. Committing it into >>> the src/ just makes the pile of not working code in src/ bigger. >> >> Yes, but on the other hand, not importing it means that the code will >> only decay faster. It's basically a damage control issue :) > No, the fusefs it is not usable in its current state (means, causing random > kernel memory corruption). The current state of it (tested against sshfs on 8-stable amd64) is: - survives blogbench runs - survives fsx runs with arguments "-W -R -L", i.e. no mmaped operations, no file size / truncate operations ... without crashing. I cannot verify kernel memory corruption but I'm running a heavy X desktop here and it survives. > Committing it causes wrong users expectation, because code does > not work, and also looks like a trick to make it appears to be maintaned, > which obviously will not happen. > > Consider this as an official objection for the import, unless somebody > is going to take the maintainership. Noted.