From owner-freebsd-current Thu Nov 21 4:11:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BDBC37B404 for ; Thu, 21 Nov 2002 04:11:48 -0800 (PST) Received: from smtp02.iprimus.net.au (smtp02.iprimus.net.au [210.50.76.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4409743E88 for ; Thu, 21 Nov 2002 04:11:46 -0800 (PST) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au ([210.50.252.164]) by smtp02.iprimus.net.au with Microsoft SMTPSVC(5.0.2195.5600); Thu, 21 Nov 2002 23:11:33 +1100 Received: from dilbert.robbins.dropbear.id.au (x1br9oy4r3v5aum3@localhost [127.0.0.1]) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6) with ESMTP id gALCBMEi072612; Thu, 21 Nov 2002 23:11:22 +1100 (EST) (envelope-from tim@dilbert.robbins.dropbear.id.au) Received: (from tim@localhost) by dilbert.robbins.dropbear.id.au (8.12.6/8.12.6/Submit) id gALCBJwG072611; Thu, 21 Nov 2002 23:11:19 +1100 (EST) (envelope-from tim) Date: Thu, 21 Nov 2002 23:11:18 +1100 From: Tim Robbins To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: [PATCH] Re: smbfs panic Message-ID: <20021121231118.A72484@dilbert.robbins.dropbear.id.au> References: <20021121185911.A64261@dilbert.robbins.dropbear.id.au> <3DDCAF3F.8AC77DE4@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3DDCAF3F.8AC77DE4@mindspring.com>; from tlambert2@mindspring.com on Thu, Nov 21, 2002 at 02:02:39AM -0800 X-OriginalArrivalTime: 21 Nov 2002 12:11:33.0868 (UTC) FILETIME=[22043AC0:01C29157] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Nov 21, 2002 at 02:02:39AM -0800, Terry Lambert wrote: > Tim Robbins wrote: > > Here's a backtrace of a smbfs panic. Looks like it does not correctly > > handle the smbfs_getpages error it is encountering and leaves garbage > > vnodes lying around. The panic probably comes from the VI_LOCK macro > > call on smbfs_node.c line 321. > > > > # cp blah.tar.gz ~tim > > cp: /home/tim/blah.tar.gz: Bad address > > > Read the list archives. We discussed this to death. The correct > thing to do is to back off and retry -- that's decimal 60, which > is hex 0x3c, which, according to /sys/netsmb/smb_rq.h is: I am aware that the "Bad address" errors have been discussed before, but I had not seen the panic on unmount/halt mentioned. Thanks for the workaround and suggested correct fix, I'll have a go at implementing that next week. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message