On Sun, May 31, 2015 at 9:13 PM, Nicholas Krause <[email protected]> wrote: > This makes the printk statement in the function, neigh_add_timer > have a loglevel of KERN_CRIT in order to get printed with the > dumping of the stack if a double timer add arises rather then > get dumped into the syslog buffer file instead in order to > allow developers to see why a stack dump has arisen. >
Instead, why not just use a WARN_ON() or something like that? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
