search for: ocfs_bh_get_data_writ

...nal "modifier" of this buffer head into that char *. Then when another process comes along as a waiter on that lock and notices the likely deadlock, he will print out the modifier and his own line number, getting right to the deadlock on the first try. In this case if I didn't make OCFS_BH_GET_DATA_WRITE a macro also, then the modifier would always come up as something like "OCFS_BH_GET_DATA_WRITE:inc/io.h:146". Not too helpful ;-) So if you ever seem to hit real deadlocks (not just a deadlock warning, but the warning plus one or more processes permanently stuck in D state) just turn...