Re: [PATCHv6 3/7] printk: introduce per-cpu safe_print seq buffer

2016-12-22 Thread Petr Mladek
On Thu 2016-12-22 10:18:41, Sergey Senozhatsky wrote: > On (12/22/16 08:53), kbuild test robot wrote: > > Hi Sergey, > > > > [auto build test ERROR on linus/master] > > [also build test ERROR on next-20161221] > > [cannot apply to v4.9] > > [if your patch is applied to the wrong git tree, please d

Re: [PATCHv6 3/7] printk: introduce per-cpu safe_print seq buffer

2016-12-21 Thread Sergey Senozhatsky
On (12/22/16 08:53), kbuild test robot wrote: > Hi Sergey, > > [auto build test ERROR on linus/master] > [also build test ERROR on next-20161221] > [cannot apply to v4.9] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: > https:/

Re: [PATCHv6 3/7] printk: introduce per-cpu safe_print seq buffer

2016-12-21 Thread kbuild test robot
Hi Sergey, [auto build test ERROR on linus/master] [also build test ERROR on next-20161221] [cannot apply to v4.9] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Sergey-Senozhatsky/printk-use-vp

[PATCHv6 3/7] printk: introduce per-cpu safe_print seq buffer

2016-12-21 Thread Sergey Senozhatsky
This patch extends the idea of NMI per-cpu buffers to regions that may cause recursive printk() calls and possible deadlocks. Namely, printk() can't handle printk calls from schedule code or printk() calls from lock debugging code (spin_dump() for instance); because those may be called with `sem->l