Hello everyone, I'd like to start a discussion about possible key/value pairs for printk() used by filesystem drivers. I am refering to the following message, please skim through it, if you haven't already: > from: Kay Sievers kay@xxxxxxxx via vger.kernel.org > to: linux-kernel@xxxxxxxxxxxxxxx > date: Wed, Apr 4, 2012 at 9:59 PM > subject: [PATCH] printk: support structured and multi-facility log > messages > Message-ID: <1333569554.864.3.camel@mop> Kay suggests improving printk() by adding key/value-formatted informaton to log events. Kay wrote: > This patch extends printk() to be able to attach arbitrary key/value > pairs to logged messages, to carry machine-readable data which > describes the context of the log message at time of its > creation. I know this is a very early stage, but the earlier we start discussing this issue, the less uncrontrolled growth there will be when this is going to be used widely some day. To throw something in the ring, I suggest we append all printk() after mounting (e.g. fill_super when autodetecting a fs) with key/value pairs like filesystem=mycoolfs device=sda1 success=true I hope this gets the discussion started! Greetings, danrl -- Dan Luedtke http://www.danrl.de -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
