Menu ▾ ▴

#83 Still need to handle lookup/remove race

closed-out-of-date
nobody
None
5
2005-09-11
2004-10-16
David Zafman
No

We need to have code again, like we did before to detect the
lookup/remove race. When it is detected we don't just d_add() in
cfs_lookup(). This occurs when a remove notify arrives at a node
which hasn't created its inode because the lookup response is in
flight. We can adapt the code in the older NSC code.

Discussion

  • Nobody/Anonymous

    Nobody/Anonymous - 2004-12-14

    Logged In: NO

    Could this be related to cfsd_lookup() kernel oops because
    its dentry has been modified during that time?

     

  • Roger Tsang

    Roger Tsang - 2005-08-26
    • status: open --> pending-out-of-date
     

  • Roger Tsang

    Roger Tsang - 2005-08-26

    Logged In: YES
    user_id=1246761

    Bug will have to be re-opened for SSI-1.9

     

  • SourceForge Robot

    SourceForge Robot - 2005-09-11

    Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     

  • SourceForge Robot

    SourceForge Robot - 2005-09-11
    • status: pending-out-of-date --> closed-out-of-date
     

Log in to post a comment.