On Wed, 19 Oct 2016 00:40:40 +0900 Sergey Senozhatsky <sergey.senozhat...@gmail.com> wrote:
> vprintk(), just like printk(), better be using per-cpu printk_func > instead of direct vprintk_emit() call. Just in case if vprintk() > will ever be called from NMI, or from any other context that can > deadlock in printk(). > > Signed-off-by: Sergey Senozhatsky <sergey.senozhat...@gmail.com> Reviewed-by: Steven Rostedt <rost...@goodmis.org> -- Steve > --- > kernel/printk/printk.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c > index d5e3973..be7f60b 100644 > --- a/kernel/printk/printk.c > +++ b/kernel/printk/printk.c > @@ -1917,7 +1917,7 @@ EXPORT_SYMBOL(vprintk_emit); > > asmlinkage int vprintk(const char *fmt, va_list args) > { > - return vprintk_emit(0, LOGLEVEL_DEFAULT, NULL, 0, fmt, args); > + return vprintk_func(fmt, args); > } > EXPORT_SYMBOL(vprintk); >