Re: [PATCH 3/3] livepatch: Use static buffer for debugging messages under rq lock

On Fri 2019-05-31 14:39:08, Josh Poimboeuf wrote: > On Fri, May 31, 2019 at 09:41:47AM +0200, Petr Mladek wrote: > > The err_buf array uses 128 bytes of stack space. Move it off the stack > > by making it static. It's safe to use a shared buffer because > > klp_try_switch_task() is called under k

Re: [PATCH 3/3] livepatch: Use static buffer for debugging messages under rq lock

On Fri 2019-05-31 14:37:52, Miroslav Benes wrote: > On Fri, 31 May 2019, Petr Mladek wrote: > > > The err_buf array uses 128 bytes of stack space. Move it off the stack > > by making it static. It's safe to use a shared buffer because > > klp_try_switch_task() is called under klp_mutex. > > > >

Re: [PATCH 3/3] livepatch: Use static buffer for debugging messages under rq lock

On Fri, May 31, 2019 at 09:41:47AM +0200, Petr Mladek wrote: > The err_buf array uses 128 bytes of stack space. Move it off the stack > by making it static. It's safe to use a shared buffer because > klp_try_switch_task() is called under klp_mutex. > > Signed-off-by: Petr Mladek > Acked-by: Mir

Re: [PATCH 3/3] livepatch: Use static buffer for debugging messages under rq lock

On Fri, 31 May 2019, Petr Mladek wrote: > The err_buf array uses 128 bytes of stack space. Move it off the stack > by making it static. It's safe to use a shared buffer because > klp_try_switch_task() is called under klp_mutex. > > Signed-off-by: Petr Mladek > Acked-by: Miroslav Benes > Revie

[PATCH 3/3] livepatch: Use static buffer for debugging messages under rq lock

The err_buf array uses 128 bytes of stack space. Move it off the stack by making it static. It's safe to use a shared buffer because klp_try_switch_task() is called under klp_mutex. Signed-off-by: Petr Mladek Acked-by: Miroslav Benes Reviewed-by: Kamalesh Babulal --- kernel/livepatch/transit