From: Miklos S. <mi...@sz...> - 2004-08-25 12:30:44
|
> So how can this happen? And more importantly who's fault is it? The node in removed from the hash chain in unhash_node(). This is called from destroy_node(), which in turn is called from do_forget(), and from lookup/create operations which were interrupted. So the only "normal" place where an inode is unhashed is the FORGET method, and it sounds quite unlikely that there would be two FORGETs for the same inode. So my guess is that this is a side effect of some other error, and valgrind may shed some light on this. Miklos |