kern/138476: [panic] [sshfs] [fuse] Almost regular panic during VFS operations; maybe related to sshfs

[Andriy Gapon]

The following reply was made to PR kern/138476; it has been noted by GNATS.

From: Andriy Gapon <avg at icyb.net.ua>
To: John Baldwin <jhb at freebsd.org>, bug-followup at freebsd.org
Cc: freebsd-fs at freebsd.org, Gavin Atkinson <gavin at freebsd.org>
Subject: Re: kern/138476: [panic] [sshfs] [fuse] Almost regular panic during
   VFS operations; maybe related to sshfs
Date: Thu, 03 Sep 2009 15:41:08 +0300

 on 03/09/2009 15:03 John Baldwin said the following:
 > On Wednesday 02 September 2009 3:00:17 pm Gavin Atkinson wrote:
 >> The following reply was made to PR kern/138476; it has been noted by GNATS.
 >>
 >> From: Gavin Atkinson <gavin at FreeBSD.org>
 >> To: bug-followup at FreeBSD.org
 >> Cc:  
 >> Subject: Re: kern/138476: [panic] [sshfs] [fuse] Almost regular panic during
 >>  VFS operations; maybe related to sshfs
 >> Date: Wed, 2 Sep 2009 19:52:46 +0100 (BST)
 >>
 >>  To submitter: Is there any chance you can try unmounting your sshfs and 
 >>  having some other fuse FS mounted, to determine if this is caused by fuse 
 >>  or sshfs?
 > 
 > You can probably narrow it down to which part of the fuse/sshfs code 
 > calls 'getnewvnode'.  This is most often done during the VFS_VGET() vfs op.  
 > It should be inserting all vnodes onto the mount list there (you can compare 
 > the code with other filesystems such as UFS to see how it should work).
 > 
 
 Looks like this could be happening in fuse_create (fuse_vnops.c).
 
 -- 
 Andriy Gapon