From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 23:11:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87173106564A; Mon, 3 Nov 2008 23:11:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5B58D8FC1D; Mon, 3 Nov 2008 23:11:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id EFC5946B09; Mon, 3 Nov 2008 18:11:38 -0500 (EST) Date: Mon, 3 Nov 2008 23:11:38 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Antony Mawer In-Reply-To: <490F77ED.9050501@mawer.org> Message-ID: References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> <490F77ED.9050501@mawer.org> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Yuri Pankov , developers@freebsd.org, Attilio Rao , freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: reproducible panic with mount_smbfs 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: Mon, 03 Nov 2008 23:11:39 -0000 On Tue, 4 Nov 2008, Antony Mawer wrote: > This probably also applies to NWFS and netncp as well -- I haven't had a > chance to test NWFS in 7.x as of yet, but will hope to do so in the coming > months... Ah, someone who actually uses netncp and nwfs! I've been trying to keep the ipx/spx code alive and working through the MPSAFE network stack work, but I'm really not set up to test that, let alone the Netware file system parts. Let us know how it goes. The netsmb and netncp code is well-structured, but designed with pre-SMPng locking primitives and network stack in mind, so will need quite a bit of work to pull forwards. As Attilio has already been running into, netsmb has rather intimate knowledge and reliance on some of the more obscure behaviors of lockmgr :-). This is something that will need to be fairly high on the list of things to change. Apple has started doing some of this in their fork of our netsmb code, but there's a lot more to do I think. Robert N M Watson Computer Laboratory University of Cambridge