On Wed, Aug 24, 2016 at 04:33:00PM -0500, Josh Poimboeuf wrote: > There's no reliable way to determine which module tainted the kernel > with CONFIG_LIVEPATCH. For example, /sys/module/<klp module>/taint > doesn't report it. Neither does the "mod -t" command in the crash tool. > > Make it crystal clear who the guilty party is by converting > CONFIG_LIVEPATCH to a module taint flag. > > This changes the behavior a bit: now the the flag gets set when the > module is loaded, rather than when it's enabled. > > Reviewed-by: Chunyu Hu <[email protected]>
Sorry, another typo. Should be: Reported-by: Chunyu Hu <[email protected]> -- Josh
