Excerpts from Chris Mason's message of 2011-03-26 08:12:04 -0400: > Excerpts from liubo's message of 2011-03-24 07:18:59 -0400: > > > > Tracepoints can provide insight into why btrfs hits bugs and be greatly > > helpful for debugging, e.g > > This is really neat, I've queued it up. Whoops, it has a lot of warnings when compiled on 32 bit machines. Please take a look: include/trace/events/btrfs.h:47:1: warning: large integer implicitly truncated to unsigned type include/trace/events/btrfs.h:47:1: warning: large integer implicitly truncated to unsigned type include/trace/events/btrfs.h:47:1: warning: large integer implicitly truncated to unsigned type include/trace/events/btrfs.h:68:1: warning: large integer implicitly truncated to unsigned type include/trace/events/btrfs.h:68:1: warning: large integer implicitly truncated to unsigned type include/trace/events/btrfs.h:68:1: warning: large integer implicitly truncated to unsigned type include/trace/events/btrfs.h:144:1: warning: large integer implicitly truncated to unsigned type -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
