From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 7 21:36:28 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34C2E16A426 for ; Mon, 7 Nov 2005 21:36:28 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D9B743D53 for ; Mon, 7 Nov 2005 21:36:05 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1540415 for multiple; Mon, 07 Nov 2005 16:37:57 -0500 Received: from localhost.baldwin.cx (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA7LZexO019048; Mon, 7 Nov 2005 16:35:50 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org, "Devon O'Dell" Date: Mon, 7 Nov 2005 16:32:49 -0500 User-Agent: KMail/1.8.2 References: <200511072000.jA7K0Whm032639@freefall.freebsd.org> In-Reply-To: <200511072000.jA7K0Whm032639@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511071632.50696.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: amd64/88249: getdents syscall fails for devfs on amd64 linuxalator X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2005 21:36:28 -0000 On Monday 07 November 2005 03:00 pm, Devon O'Dell wrote: > The long discussion ended up implying several things: > > d) The issue probably isn't limited to linuxulator, but to any > filesystem that uses cookies and exports devfs. Thus, panics (or > hangs) will probably occur for devfs being exported over AFS or NFS. Well, it shouldn't panic, that's for sure. > The attached patch does two things: > > a) If we are provided with cookie information in devfs, we currently > do not support this. This means we cannot export devfs over network > mounts, which I don't view as a problem (but would be a cool > feature). Actually, it would be a worse than useless feature when you consider dynamic major number allocation (so that /dev/cuad0 on one machine might map to /dev/acd0 on another machine) not to mention the fact that on FreeBSD, at least, we don't have specfs anymore, so you can't look devices up by just major/minor, but it has to be by their name through an instance of devfs. So, only non-FreeBSD clients could even use the exported char devs, and FreeBSD char devs are less than useless on non-FreeBSD operating systems. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org