On Tue, 20 Jan 2015, Josh Poimboeuf wrote: > Yeah, maybe, depending on the nature of the bug. > > > WARN_ON_RATELIMIT? > > Since this warning should never happen unless there's a code bug, I > think WARN_ON_ONCE should be sufficient?
Yeah. The stacktrace is likely not to point to the source of the problem anyway, so spamming dmesg with it is rather pointless. I've changed WARN_ON() in ftrace handler to WARN_ON_ONCE() and applied. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
