Changes between Initial Version and Version 1 of Ticket #9839


Ignore:
Timestamp:
Dec 7, 2013, 7:55:45 PM (10 years ago)
Author:
bonefish
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9839 – Description

    initial v1  
    55An IMO cleaner alternative would be to change the interface and semantics of the `get_vnode()` hook. It would be required to create the vnode (via `publish_vnode()` or a new interface). We would have to push the burden of dealing with concurrent invocations to the hook, though.
    66
    7 It is not understood yet whether the described issue is related to #5262. Here the panic reports the `vnode->node` to be NULL, while that isn't the case in #5262.
     7This issue is somewhat related to #5262 in that there the problem is also that `create_new_vnode_and_lock()` reports a pre-existing vnode, although in that case the vnode is about to be deleted and already no longer known to the FS (cf. ticket:5262#comment:24).