Skip to contentSkip to conversation

printk and kdb - dev_<level> not trapped/forwarded

DISCUSSION Joe Perches 1 participant 1 message Feb 21, 2014

lore
Share & tools
lore
#0 lore raw

dev_<level> output does not use printk() but directly calls vprintk_emit().

kdb only traps direct printk() calls.

So, kdb hasn't emitted any dev_<level> or netdev_<level> output since structured logging and vprintk_emit() was introduced a couple of years ago.

It seems no one has cared.

Maybe the kdb handling should be removed?