linux-kernel - Re: [PATCHSET] printk: implement printk_header() and merging printk, take #2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47968432.2090304@gmail.com>
Date:	Wed, 23 Jan 2008 09:02:58 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
CC:	Matthew Wilcox <matthew@....cx>, randy.dunlap@...cle.com,
	daniel.ritz-ml@...ssonline.ch, jeff@...zik.org,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: [PATCHSET] printk: implement printk_header() and merging printk,
 take #2

Jan Engelhardt wrote:
> On Jan 23 2008 08:51, Tejun Heo wrote:
>> What do you think about the second suggestion then?
>>
>> ata1.00: line0
>> ata1.00  line1
>> ata1.00  line2
>>
>> It allows you to grab for the header && has indication for message
>> boundaries.
> 
> Then again, why not "[ata1.00] line0", then it matches what sd_mod does :)

Well, that's fine too but using ':' is much more common.  Just take a
look at the boot log and if we go with '[]', any ideas on how to
indicate multiline messages?

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/