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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 4 Nov 2016 00:28:27 +0100
From:   Jan Kara <jack@...e.cz>
To:     Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc:     Joe Perches <joe@...ches.com>, Jiri Kosina <jikos@...nel.org>,
        Theodore Tso <tytso@....edu>, Hannes Reinecke <hare@...e.de>,
        Jan Kara <jack@...e.com>, Petr Mladek <pmladek@...e.com>,
        linux-kernel@...r.kernel.org
Subject: Re: printk considered harmful (was: [TECH TOPIC] asynchronous printk)

On Fri 04-11-16 03:01:31, Sergey Senozhatsky wrote:
> fix a typo
> 
> On (11/04/16 02:31), Sergey Senozhatsky wrote:
> [..]
> > #4 console semaphore
> > discussion outcome:
> >   we agreed that we can do better here and that it makes sense to do
> 				    ^^^^ IOW, console semaphore thing
> 				    can be improved
> 
> >   what's been proposed in my slides. but, I keep it as a low priority.
> >   frankly. I'd be happy to see #1-#3 in the mainline in 9-12 months.
> 				 ^^^^ #1-#2, of course. but #1 consists
> 				 of 2 steps.
> 
> I'm still not entirely sure if I want to split async pintk and printk
> deadlock rework. these things want to come together, for a number of
> reasons. or, at least, push the async printk before printk deadlock
> rework.

Yep, please push async printk patches soon. IMHO there's no reason to wait
with that. You can create a git tree with printk patches and push it directly
to Linus since he seems to be fine with the approach...

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR

Powered by blists - more mailing lists