[prev in list] [next in list] [prev in thread] [next in thread] 

List:       haiku-bugs
Subject:    [haiku-bugs] Re: [Haiku] #3159: [kernel] PANIC: ASSERT FAILED: vnode->ref_count ==0 && vnode->busy
From:       "axeld" <trac () haiku-os ! org>
Date:       2012-03-31 21:19:30
Message-ID: 055.ebfbd4ac568d70a0229b53947f99157a () haiku-os ! org
[Download RAW message or body]

#3159: [kernel] PANIC: ASSERT FAILED: vnode->ref_count ==0 && vnode->busy
-----------------------------+----------------------------
   Reporter:  diver          |      Owner:  axeld
       Type:  bug            |     Status:  new
   Priority:  normal         |  Milestone:  R1
  Component:  System/Kernel  |    Version:  R1/Development
 Resolution:                 |   Keywords:
 Blocked By:                 |   Blocking:  8402, 8419
Has a Patch:  0              |   Platform:  All
-----------------------------+----------------------------

Comment (by axeld):

 I don't have any idea what is causing the issue either. The only reason
 this could happen is that someone else opens the inode in-between -
 directly, via inode ID. This again cannot happen, as Ingo pointed out,
 since the node is marked busy, and get_vnode() will fail in that case.

 In any case, Urias just confirmed that the ref_count is 1 for the test he
 is running. I didn't manage to reproduce the issue yet the way he
 described.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/3159#comment:12>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

[prev in list] [next in list] [prev in thread] [next in thread]