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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Sep 2017 13:42:40 +0900 From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com> To: Joe Perches <joe@...ches.com> Cc: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>, Linus Torvalds <torvalds@...ux-foundation.org>, 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 (09/17/17 20:07), Joe Perches wrote: > On Mon, 2017-09-18 at 11:55 +0900, Sergey Senozhatsky wrote: > > Try git grep KERN_SOH. > > > > what for? > > Did you read your own email? > > > printk(KERN_SOH_ASCII %d " foo bar / %s %s\n", "foo", "bar"); > > _nothing_ looks like that. OK... got it. I obviously meant the way we treat the prefix - KERN_SOH_ASCII and int loglevel that we store in msg->level - and not the way the prefix actually looks (KERN_SOH %c). I thought that was kinda clear. anyway, the point of my email was completely different. sorry if that confused you, or anybody else. > It wouldn't even compile. well, don't try to compile my emails ;) -ss
Powered by blists - more mailing lists