Messages in this thread | | | Date | Tue, 6 Mar 2012 13:51:37 -0500 | From | Dave Jones <> | Subject | inode->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: https://bugzilla.redhat.com/show_bug.cgi?id=784741 https://bugzilla.redhat.com/show_bug.cgi?id=799229 https://bugzilla.redhat.com/show_bug.cgi?id=799692
Dave
| |