Re: [PATCH 4.19 130/133] printk: queue wake_up_klogd irq_work only if per-CPU areas are ready

2020-07-20 Thread Sergey Senozhatsky
On (20/07/21 00:05), Pavel Machek wrote: > > From: Sergey Senozhatsky > > > > commit ab6f762f0f53162d41497708b33c9a3236d3609e upstream. > > [..] > > Is this still needed in 4.19? 1b710b1b10ef was reverted in 4.19, so > there should not be any user-visible problems... printk_deferred() is

Re: [PATCH 4.19 130/133] printk: queue wake_up_klogd irq_work only if per-CPU areas are ready

2020-07-20 Thread Pavel Machek
Hi! > From: Sergey Senozhatsky > > commit ab6f762f0f53162d41497708b33c9a3236d3609e upstream. > > printk_deferred(), similarly to printk_safe/printk_nmi, does not > immediately attempt to print a new message on the consoles, avoiding > calls into non-reentrant kernel paths, e.g. scheduler or

[PATCH 4.19 130/133] printk: queue wake_up_klogd irq_work only if per-CPU areas are ready

2020-07-20 Thread Greg Kroah-Hartman
From: Sergey Senozhatsky commit ab6f762f0f53162d41497708b33c9a3236d3609e upstream. printk_deferred(), similarly to printk_safe/printk_nmi, does not immediately attempt to print a new message on the consoles, avoiding calls into non-reentrant kernel paths, e.g. scheduler or timekeeping, which