Re: [regression] tracing: kmemleak warning in allocate_cmdlines_buffer()

On Wed, 14 Feb 2024 17:30:40 +0200 Kalle Valo wrote: > Although the patch didn't apply for me as in my tree the functions are > in kernel/trace/trace.c. I don't know what happened so as a quick hack I > just manually added the three lines to my version of trace.c. Let me > know if there's a git t

Re: [regression] tracing: kmemleak warning in allocate_cmdlines_buffer()

On Wed, 14 Feb 2024 17:30:40 +0200 Kalle Valo wrote: > Although the patch didn't apply for me as in my tree the functions are > in kernel/trace/trace.c. I don't know what happened so as a quick hack I > just manually added the three lines to my version of trace.c. Let me > know if there's a git t

Re: [regression] tracing: kmemleak warning in allocate_cmdlines_buffer()

Steven Rostedt writes: > On Wed, 14 Feb 2024 14:50:56 +0200 > Kalle Valo wrote: > >> Hi Steven, >> >> I upgraded our ath11k test setup to v6.8-rc4 and noticed a new kmemleak >> warning in the log: > > Thanks for the report. > >> >> unreferenced object 0x8881010c8000 (size 32760): >> comm

Re: [regression] tracing: kmemleak warning in allocate_cmdlines_buffer()

On Wed, 14 Feb 2024 14:50:56 +0200 Kalle Valo wrote: > Hi Steven, > > I upgraded our ath11k test setup to v6.8-rc4 and noticed a new kmemleak > warning in the log: Thanks for the report. > > unreferenced object 0x8881010c8000 (size 32760): > comm "swapper", pid 0, jiffies 4294667296 >

[regression] tracing: kmemleak warning in allocate_cmdlines_buffer()

Hi Steven, I upgraded our ath11k test setup to v6.8-rc4 and noticed a new kmemleak warning in the log: unreferenced object 0x8881010c8000 (size 32760): comm "swapper", pid 0, jiffies 4294667296 hex dump (first 32 bytes): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ...