From owner-freebsd-current Wed Oct 23 2: 0:21 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 D535837B401; Wed, 23 Oct 2002 02:00:19 -0700 (PDT) Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B94543E65; Wed, 23 Oct 2002 02:00:14 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0050.cvx22-bradley.dialup.earthlink.net ([209.179.198.50] helo=mindspring.com) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 184HN2-0002VP-00; Wed, 23 Oct 2002 02:00:08 -0700 Message-ID: <3DB664D0.FE0B8018@mindspring.com> Date: Wed, 23 Oct 2002 01:58:56 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: kalts@estpak.ee Cc: Maxime Henrion , Vitaly Markitantov , jhb@freebsd.org, current@freebsd.org Subject: Re: smbfs broken? References: <20021022110135.GA31643@iron.del.local> <20021022112320.GF26605@elvis.mu.org> <20021022142954.GA3206@tiiu.internal> <3DB5A3BD.77138903@mindspring.com> <20021022195301.GB4048@tiiu.internal> <3DB5B335.34F42350@mindspring.com> <20021023065509.GA1178@tiiu.internal> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 Vallo Kallaste wrote: > > I don't understand, then. There should be no other way that an ffs_write > > call can trap to needing an SMBFS page: > > > > #22 0xc03902a8 in calltrap () at {standard input}:99 > > #23 0xc033af01 in ffs_write (ap=0xd66ebbe8) at ../../../ufs/ffs/ffs_vnops.c:810 > > #24 0xc029b74d in vn_write (fp=0xc40341a4, uio=0xd66ebc68, > > active_cred=0xc4251d00, flags=0, td=0xc13534e0) at vnode_if.h:417 > > #25 0xc0259a75 in dofilewrite (td=0xc13534e0, fp=0xc40341a4, fd=4, > > buf=0x2805b000, nbyte=0, offset=0, flags=0) at file.h:215 > > #26 0xc0259909 in write (td=0xc13534e0, uap=0xd66ebd10) > > at ../../../kern/sys_generic.c:329 > > --- > > > > You *must* be doing something that causes an SMBFS object to act as > > backing store for an FFS. > > You know better, sure, but nevertheless I'm not doing anything what > can cause it. Perhaps a bug somewhere. My guess is in the "?" routines that you didn't backtrace for us; perhaps what happened was that the stack frame screwed up, and implicated code that was not a fault. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message