On Tue, Nov 29, 2022 at 04:35:10AM +0100, Mirsad Goran Todorovac wrote:
> On 10. 11. 2022. 10:20, Greg KH wrote:
> > On Thu, Nov 10, 2022 at 05:57:57AM +0100, Mirsad Goran Todorovac wrote:
> > > On 04. 11. 2022. 11:40, Mirsad Goran Todorovac wrote:
> > >
> > > > Dear Sirs,
> > > >
> > > > When bu
On 10. 11. 2022. 10:20, Greg KH wrote:
On Thu, Nov 10, 2022 at 05:57:57AM +0100, Mirsad Goran Todorovac wrote:
On 04. 11. 2022. 11:40, Mirsad Goran Todorovac wrote:
Dear Sirs,
When building a RPM 6.1.0-rc3 for AlmaLinux 8.6, I have enabled
CONFIG_DEBUG_KMEMLEAK=y
and the result showed an unre
On 10.11.2022. 10:20, Greg KH wrote:
On Thu, Nov 10, 2022 at 05:57:57AM +0100, Mirsad Goran Todorovac wrote:
On 04. 11. 2022. 11:40, Mirsad Goran Todorovac wrote:
Dear Sirs,
When building a RPM 6.1.0-rc3 for AlmaLinux 8.6, I have enabled
CONFIG_DEBUG_KMEMLEAK=y
and the result showed an unrefe
On 10.11.2022. 9:28, Thorsten Leemhuis wrote:
This bug is confirmed in 6.1-rc4, among the "thermald" and "systemd-dev"
kernel memory leaks, potentially exposing race conditions or other more
serious bug.
Maybe, but that sadly is also true for a lot of other known issues, for
example those in th
On Thu, Nov 10, 2022 at 05:57:57AM +0100, Mirsad Goran Todorovac wrote:
> On 04. 11. 2022. 11:40, Mirsad Goran Todorovac wrote:
>
> > Dear Sirs,
> >
> > When building a RPM 6.1.0-rc3 for AlmaLinux 8.6, I have enabled
> > CONFIG_DEBUG_KMEMLEAK=y
> > and the result showed an unreferenced object in
On 04. 11. 2022. 11:40, Mirsad Goran Todorovac wrote:
Dear Sirs,
When building a RPM 6.1.0-rc3 for AlmaLinux 8.6, I have enabled
CONFIG_DEBUG_KMEMLEAK=y
and the result showed an unreferenced object in kworker process:
# cat /sys/kernel/debug/kmemleak
unreferenced object 0xa01dabff6100 (s