[lkml]   [2012]   [Mar]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjectinode->i_wb_list corruption.
    We've had three separate reports against 3.2.x recently where the linked list debugging
    is getting tripped up by the prev->next pointer being null instead of pointing
    to the current list entry while walking the i_wb_list

    Call traces are slightly different each time, but all end up walking i_wb_list
    in dput -> d_kill -> i_put -> evict -> inode_wb_list_del

    What protects that list ? It looks to be just bdi->wb.list_lock ?

    full reports at:


     \ /
      Last update: 2012-03-06 19:53    [W:0.018 / U:74.296 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site