On Mon, 2022-07-25 at 12:04 +0206, John Ogness wrote: > I suppose this patch side-steps the splat because the first > vsnprintf() already triggered the random bytes for the pointer > hash. Yeah, sounds right. > I am preparing a new series that addresses this by completely removing > interrupt disabling from the printk() path. This required changes to the > printk_enter() macro, recursion handling, and the printk-ringbuffer > itself. > > The focus of my new series are the various non-RT issues reported during > the early 5.19-rc cycles. I still need more time to get the series into > shape for LKML. > > If Mike's patch is reliably side-stepping the issue, feel free to take > it. It does, but I'm in no rush... and it is a bandaid :) -Mike
