From: Tilman Schmidt <tilman@imap.cc>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
Andrew Morton <akpm@osdl.org>,
linux-usb-devel@lists.sourceforge.net, hjlipp@web.de,
linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH] reduce syslog clutter (take 2)
Date: Thu, 09 Mar 2006 20:17:20 +0100 [thread overview]
Message-ID: <44107F40.4000500@imap.cc> (raw)
In-Reply-To: <9a8748490603091058l75aacacsfc5fdba3981fb074@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]
On 09.03.2006 19:58, Jesper Juhl wrote:
> On 3/9/06, Tilman Schmidt <tilman@imap.cc> wrote:
>
>>On 09.03.2006 17:34, Randy.Dunlap wrote:
>>
>>>On Thu, 9 Mar 2006 03:02:57 -0800 Andrew Morton wrote:
>>>
>>>>Tilman Schmidt <tilman@imap.cc> wrote:
>>>>
>>>>>The current versions of the err() / info() / warn() syslog macros
>>>>>insert __FILE__ at the beginning of the message, which expands to
>>>>>the complete path name of the source file within the kernel tree.
>>>>>
>>>>>With the following patch, when used in a module, they'll insert the
>>>>>module name instead, which is significantly shorter and also tends to
>>>>>be more useful to users trying to make sense of a particular message.
>>>>
>>>>Personally, I prefer to see filenames. Or function names. Sometimes it's
>>>>rather unobvious how to go from module name to filename, due to a) multiple
>>>>.o files being linked together, b) subsystems which insist on #including .c
>>>>files in .c files (usb...) and c) the module system's cute habit of
>>>>replacing underscores with dashes in module names.
>>>
>>>True, just using module->name or whatever means that we would
>>>(often?) have to do a lookup to see what source file it was in.
>>
>>That would be a valid point for debugging messages. However, we are
>>talking about messages to users here. I maintain that the additional 20
>>characters in:
>>
>>Feb 21 00:12:13 gx110 kernel: drivers/isdn/gigaset/i4l.c:
>>ISDN_CMD_SETL3: invalid protocol 42
>>
>>as opposed to:
>>
>>Feb 21 00:12:13 gx110 kernel: gigaset: ISDN_CMD_SETL3: invalid protocol 42
>>
>>do not provide any useful information for that clientele. They just push
>
> The filename may not be useful to the user, but the instant the user decides to
> submit a bugreport to LKML or elsewhere it becomes useful.
Then why does the majority of kernel messages not include a filename?
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2006-03-09 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 22:54 [PATCH] reduce syslog clutter (take 2) Tilman Schmidt
2006-03-09 5:47 ` Randy.Dunlap
2006-03-09 10:15 ` Tilman Schmidt
2006-03-09 11:02 ` Andrew Morton
2006-03-09 16:34 ` Randy.Dunlap
2006-03-09 18:43 ` Tilman Schmidt
[not found] ` <9a8748490603091058l75aacacsfc5fdba3981fb074@mail.gmail.com>
2006-03-09 19:17 ` Tilman Schmidt [this message]
2006-03-09 21:03 ` Andrew Morton
2006-03-09 21:18 ` Pete Zaitcev
2006-03-09 22:42 ` Greg KH
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=44107F40.4000500@imap.cc \
--to=tilman@imap.cc \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=hjlipp@web.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=rdunlap@xenotime.net \
/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