From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Luedtke Subject: key/value-pairs for improved printk() Date: Fri, 06 Apr 2012 22:23:08 +0200 Message-ID: <1333743788.16664.6.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: kay@vrfy.org To: linux-fsdevel@vger.kernel.org Return-path: Received: from mail.nonattached.net ([193.160.39.30]:37234 "EHLO mail.nonattached.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932376Ab2DFUci (ORCPT ); Fri, 6 Apr 2012 16:32:38 -0400 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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@vrfy.org via vger.kernel.org > to: linux-kernel@vger.kernel.org > 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