On Thu, Apr 17, 2014 at 07:35:14PM -0700, Lin Ming wrote: > Added a barrier(), but still panic. Wrong kind of barrier ;-) This one just says the compiler that it shouldn't reorder; it doesn't help other CPUs at all. Read Documentation/memory-barriers.txt for details, but I seriously wonder if we _want_ to mess with barriers in the first place... -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
