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
| ||
|
Message-ID: <1505701349.12022.1.camel@perches.com> Date: Sun, 17 Sep 2017 19:22:29 -0700 From: Joe Perches <joe@...ches.com> To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>, Linus Torvalds <torvalds@...ux-foundation.org> Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Petr Mladek <pmladek@...e.com>, Steven Rostedt <rostedt@...dmis.org>, Pavel Machek <pavel@....cz>, Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>, Jiri Slaby <jslaby@...e.com>, Andreas Mohr <andi@...as.de>, Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: printk: what is going on with additional newlines? On Mon, 2017-09-18 at 09:46 +0900, Sergey Senozhatsky wrote: > there is another reason why I think that, yes, we probably better do > it some other way. and the reason is that not every message that looks > like !PREFIX (does not start with KERN_SOH_ASCII) is _actually_ a > !PREFIX message. the normal/usual way is to have something like > > printk(KERN_SOH_ASCII %d " foo bar / %s %s\n", "foo", "bar"); > > but some messages look like > > printk("%s", KERN_SOH_ASCII %d "foo bar\n"); There are no messages that look like that. There are 2 entries somewhat like that though net/bridge/netfilter/ebt_log.c: printk(KERN_SOH "%c%s IN=%s OUT=%s MAC source = %pM MAC dest = %pM proto = 0x%04x", net/netfilter/nf_log_common.c: nf_log_buf_add(m, KERN_SOH "%c%sIN=%s OUT=%s ",
Powered by blists - more mailing lists