Re: [PATCH] printk: fix possible reuse of va_list variable

2018-05-17 Thread Petr Mladek
On Fri 2018-05-11 20:02:31, Tetsuo Handa wrote: > >From 766cf72b5fdc00d1cf5a8ca2c6b23ebb75e2b4d4 Mon Sep 17 00:00:00 2001 > From: Tetsuo Handa > Date: Fri, 11 May 2018 19:54:19 +0900 > Subject: [PATCH] printk: fix possible reuse of va_list variable > > I noticed that there

Re: [PATCH] printk: fix possible reuse of va_list variable

2018-05-11 Thread Sergey Senozhatsky
On (05/11/18 20:02), Tetsuo Handa wrote: > I noticed that there is a possibility that printk_safe_log_store() causes > kernel oops because "args" parameter is passed to vsnprintf() again when > atomic_cmpxchg() detected that we raced. Fix this by using va_copy(). > > Signed-off-by: Tetsuo Handa >

[PATCH] printk: fix possible reuse of va_list variable

2018-05-11 Thread Tetsuo Handa
>From 766cf72b5fdc00d1cf5a8ca2c6b23ebb75e2b4d4 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Fri, 11 May 2018 19:54:19 +0900 Subject: [PATCH] printk: fix possible reuse of va_list variable I noticed that there is a possibility that printk_safe_log_store() causes kernel oops because &q