On (24/09/26 15:32), Petr Mladek wrote: > On Thu 2024-09-26 13:07:15, Sergey Senozhatsky wrote: > > Greetings, > > > > Ran into the following issue today. It's sort of interesting, not sure > > what even to do about it. The > > > > uart -> tty -> mm /* kmalloc -> kmemleak */ > > > > chain looks problematic, it certainly overlaps with > > > > mm -> printk -> uart /* which can kmalloc and re-enter mm -> kmemleak? */ > > I believe that it will get solved by the uart console driver > conversion to nbcon. I should remove the path: > > printk -> uart > > or more precisely, it should remove the path: > > console_owner --> &port_lock_key > > The patchset with the uart 8250 console driver conversion is still > pending a review, see the last version at > https://lore.kernel.org/r/20240913140538.221708-1-john.ogness@xxxxxxxxxxxxx It does fix the issue for me, you are right. Thanks for the pointers.
