[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161031085742.GO12522@suse.cz>
Date: Mon, 31 Oct 2016 09:57:42 +0100
From: David Sterba <dsterba@...e.cz>
To: Petr Mladek <pmladek@...e.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Chris Mason <clm@...com>, Josef Bacik <jbacik@...com>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Joe Perches <joe@...ches.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, linux-kernel@...r.kernel.org,
Jason Wessel <jason.wessel@...driver.com>
Subject: Re: [PATCH 3/4] printk/btrfs: Handle more message headers
On Thu, Oct 27, 2016 at 05:52:53PM +0200, Petr Mladek wrote:
> The commit 4bcc595ccd80decb4245096e ("printk: reinstate KERN_CONT for
> printing continuation lines") allows to define more message headers
> for a single message. The motivation is that continuous lines might
> get mixed. Therefore it make sense to define the right log level
> for every piece of a cont line.
>
> The current btrfs_printk() macros do not support continuous lines at
> the moment. But better be prepared for a custom messages and avoid
> potential "lvl" buffer overflow.
I don't think we'll want to support continued lines. The macros just
print additional information about the filesystem and the message is
supposed to be on one line. If there's multi-line string, the raw printk
calls are used (and currently only for debugging purposes).
Acked-by: David Sterba <dsterba@...e.com>
Powered by blists - more mailing lists