From: Dan Luedtke <mail@danrl.de>
To: linux-fsdevel@vger.kernel.org
Cc: kay@vrfy.org
Subject: key/value-pairs for improved printk()
Date: Fri, 06 Apr 2012 22:23:08 +0200 [thread overview]
Message-ID: <1333743788.16664.6.camel@localhost> (raw)
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
next reply other threads:[~2012-04-06 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 20:23 Dan Luedtke [this message]
2012-04-06 23:58 ` key/value-pairs for improved printk() Al Viro
2012-04-07 9:41 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1333743788.16664.6.camel@localhost \
--to=mail@danrl.de \
--cc=kay@vrfy.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).