On Fri, 2022-06-24 at 16:39 +0200, Sebastian Andrzej Siewior wrote: > On 2022-06-24 16:37:25 [+0206], John Ogness wrote: > > On 2022-06-24, John Ogness <john.ogness@xxxxxxxxxxxxx> wrote: > > > As to this the actual problem reported in this thread, I believe > > > this > > > patch solves it: > > > > > > https://lore.kernel.org/lkml/20220609121709.12939-1-Jason@xxxxxxxxx > > > > There was a cleaner v2 later in the thread: > > > > https://lore.kernel.org/lkml/20220609123319.17576-1-Jason@xxxxxxxxx > > In that case v5.19-rc3-rt5 should no longer show it but I am still > confused why we need to disable interrupts within vsnprintf(). It says they're disabled to simplify recursion tracking. I was thinking maybe replace that with a local lock, but then the below happened, rendering that little wart kinda moot for the moment. 07a22b61946f Revert "printk: add functions to prefer direct printing" 5831788afb17 Revert "printk: add kthread console printers" 2d9ef940f89e Revert "printk: extend console_lock for per-console locking" 007eeab7e9f0 Revert "printk: remove @console_locked" 05c96b3713aa Revert "printk: Block console kthreads when direct printing will be required" 20fb0c8272bb Revert "printk: Wait for the global console lock when the system is going down" -Mike
