Re-sending compressed attachments to fit into the size limit. On 27. 10. 2022. 20:03, Mirsad Goran Todorovac wrote:
P.S.Forgot another useful thing you've mentioned: please find attached the dmesg output.Good luck! Mirsad On 27. 10. 2022. 00:48, srinivas pandruvada wrote:On Wed, 2022-10-26 at 19:52 +0200, Mirsad Goran Todorovac wrote:Dear all, On 24. 10. 2022. 20:56, Mirsad Goran Todorovac wrote:On 24. 10. 2022. 20:39, srinivas pandruvada wrote:Thank you for the patch. Unfortunately, when applied to v6.0.3 it didn't fix the issue.Thanks for the test. I copied to acpi and acpica mailing list. Someone can tell us what is this call doing wrong here.I have worse news: after every # systemctl stop thermald # systemctl start thermald the number of leaks increases by one allocated block (apparently 80 bytes). The effect appears to be cummulative. Please find the results of the MEMLEAK scan in the attachment. In theory, motivated adversary could theoretically exhaust i.e. 8 GiB in a loop of 10 million thermald stops/starts,Of course it needs to be debugged. To start/stop systemctl service you need root access. If you have root access, there are other worse things can be done. Thanks, Srinivason my laptop and 2 sec for stop+start, it would be approx. 230 days. Hope this helps. Mirsad -- Mirsad Goran Todorovac Sistem inženjer Grafički fakultet | Akademija likovnih umjetnosti Sveučilište u Zagrebu-- Mirsad Goran Todorovac Sistem inženjer Grafički fakultet | Akademija likovnih umjetnosti Sveučilište u Zagrebu
-- Mirsad Goran Todorovac Sistem inženjer Grafički fakultet | Akademija likovnih umjetnosti Sveučilište u Zagrebu -- System engineer Faculty of Graphic Arts | Academy of Fine Arts University of Zagreb, Republic of Croatia The European Union
Attachment:
thermald-memleak.lshw.txt.gz
Description: application/gzip
Attachment:
thermald-memleak.wsleep1.txt.gz
Description: application/gzip
Attachment:
thermald_memleak_dmesg.txt.gz
Description: application/gzip
