On Wed, 7 Mar 2012, Glauber Costa wrote: > > I don't suspect we'll be very popular if we try to remove it, I can see > > how it would be useful when BUG() is used when the problem isn't really > > fatal (to stop something like disk corruption), like the above case isn't. > I guess everyone that is able to track the problem back to an instance of > BUG(), be skilled enough to be sure it is not fatal, and then recompile the > kernel with this option (that I bet many of us didn't even know that existed), > can very well just change it to a WARN_*, (and maybe patch it upstream). > That's the point of the next patch which changes this to a WARN_ON_ONCE(1) because all of the BUG()'s that it changes in mm/mempolicy.c aren't fatal. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>