On (12/22/16 23:01), Tetsuo Handa wrote:
> > On (12/22/16 19:27), Tetsuo Handa wrote:
> > > Thank you. I tried "[PATCHv6 0/7] printk: use printk_safe to handle printk()
> > > recursive calls" at https://lkml.org/lkml/2016/12/21/232 on top of linux.git
> > > as of commit 52bce91165e5f2db "splice: reinstate SIGPIPE/EPIPE handling", but
> > > it turned out that your patch set does not solve this problem.
> > > 
> > > I was assuming that sending to consoles from printk() is offloaded to a kernel
> > > thread dedicated for that purpose, but your patch set does not do it.
> > 
> > sorry, seems that I didn't deliver the information properly.
> > 
> > https://gitlab.com/senozhatsky/linux-next-ss/commits/printk-safe-deferred
> > 
> > there are 2 patch sets. the first one is printk-safe. the second one
> > is async printk.
> > 
> > 9 patches in total (as of now).
> > 
> > can you access it?
> 
> "404 The page you're looking for could not be found."
> 
> Anonymous access not supported?

oops... hm, dunno, it says

: Visibility Level (?)
:
: Public
: The project can be cloned without any authentication.

I'll switch to github then may be.

attached 9 patches.

NOTE: not the final version.


	-ss