On Tue, Apr 24, 2018 at 01:03:13PM +0800, Qu Wenruo wrote: > It's pretty handy if we can get debug output for locking status of an > extent buffer, specially for race related debugging. > > So add the following output for btrfs_print_tree() and > btrfs_print_leaf(): > - refs > - write_locks (as w:%d) > - read_locks (as r:%d) > - blocking_writers (as bw:%d) > - blocking_readers (as br:%d) > - spinning_writers (as sw:%d) > - spinning_readers (as sr:%d) > - lock_owner > - current->pid
This is fine > + btrfs_info(eb->fs_info, I'd rather make that btrfs_debug, but info is fine as long as it's under CONFIG_BTRFS_DEBUG. > +"refs %u lock(w:%u r:%u bw:%u br:%u sw:%u sr:%u) lock_owner %u current %u", This is not :) but I'll fix that according to the above. Reviewed-by: David Sterba <dste...@suse.com> -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
