Re: [PATCH] printk: Enough to disable preemption in printk deferred context

[John Ogness]

On 2023-04-19, Petr Mladek <pmladek@xxxxxxxx> wrote:
> it is safe to interrupt one writer now. The preemption still
> has to be disabled because the deferred context is CPU specific.

Really it is enough to disable migration.

We need to keep an eye on the usage of this function. By allowing
interrupts and preemption, it means that other printk's on that CPU will
also be deferred if the context interrupted within the deferred block.

John