From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763354AbcJaI5s (ORCPT ); Mon, 31 Oct 2016 04:57:48 -0400 Received: from mx2.suse.de ([195.135.220.15]:42904 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763115AbcJaI5p (ORCPT ); Mon, 31 Oct 2016 04:57:45 -0400 Date: Mon, 31 Oct 2016 09:57:42 +0100 From: David Sterba To: Petr Mladek Cc: Linus Torvalds , Chris Mason , Josef Bacik , Sergey Senozhatsky , Steven Rostedt , Andrew Morton , Joe Perches , Jaroslav Kysela , Takashi Iwai , linux-kernel@vger.kernel.org, Jason Wessel Subject: Re: [PATCH 3/4] printk/btrfs: Handle more message headers Message-ID: <20161031085742.GO12522@suse.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Petr Mladek , Linus Torvalds , Chris Mason , Josef Bacik , Sergey Senozhatsky , Steven Rostedt , Andrew Morton , Joe Perches , Jaroslav Kysela , Takashi Iwai , linux-kernel@vger.kernel.org, Jason Wessel References: <1477583574-30988-1-git-send-email-pmladek@suse.com> <1477583574-30988-4-git-send-email-pmladek@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1477583574-30988-4-git-send-email-pmladek@suse.com> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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